feat(http gateway)

[cong-or]

Initial HTTP gateway scaffold.

Future PRs which expand on this:

• extension of connection manager to include event tracking.
• example hello world kv app with defined API surface and wasm component to showcase - "how everything works in tandem"

[cong-or]

Am I correct that mechanics of this http extensions is follows right now: http runtime extensions receives request -> for the received request transformed to hermes event -> hermes http event is sent to event queue -> hermes event executes inside wasm -> original request sender receives response after the successful event execution as a part of the event processing function.

What happens if event will be not executed inside wasm (because event queue does not provide such guaranties). Does the user will receive some response at this case ?

yes correct. But the next step is to add event tracking and management - the connection manager is a start for this. We will think about it in more detail then. At the moment we just respond like this - the event either returns Some or None and the http response mirrors this back to the client.

[cong-or]

re-opening with dependency tracking changes.