feat(464): add async actions consumer SDK to act API

[Hamsajj]

Ticket(s)

gatewayd-io/gatewayd#464

Description

Adds a consumer SDK to let plugins consume async actions that has been put into a queue and process them.

Related PRs

Development Checklist

• I have added a descriptive title to this PR.
• I have squashed related commits together.
• I have rebased my branch on top of the latest main branch.
• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have added docstring(s) and type annotations to my code.
• I have made corresponding changes to the documentation (docs).
• I have added tests for my changes.

Legal Checklist

• I have read the CONTRIBUTING document.
• I have read and understood the Code of Conduct.
• I have read and agreed to the Apache CLA (required).
• I have read and agreed to the LICENSE (required).

[mostafa]

LGTM! Only two minor comments.

Also, zerolog is the logger for GatewayD and plugins use go-hclog instead, like this one that is referenced here and used like this. Since GatewayD collects logs from plugins and converts them to zerolog via the hclog-adapter, if we use zerolog in the plugins, we won't be able to see the consumer logs in the collected logs.

If the code is going to be used in the plugins as well, we should account for both of these loggers or have WithZeroLogLogger and WithHcLogLogger functions to create the Consumer object.

Logger should be fixed.

[Hamsajj]

As it is not used in gatewayd directly (only used in tests), I removed the support for zerolog and changed it to use hclog.

[mostafa]

@Hamsajj

I was thinking about a LoggerWrapper that can support multiple loggers under the hood, like the multilogger that is described in this article. This becomes important when we want to implement gatewayd-io/gatewayd#472, but that's out of scope of this ticket, so I'll create another ticket to handle this.