Support Reactor Wasm Modules for takeoff and ATC

[davidmdm]

Currently the only wasm module that is used is the main module used to compute the resources to deploy.

This means all the code needed must be deployed from one source language or ecosystem.

As an example, yoke provides Go packages to render helm charts. However if my language of choice was zig or rust, in order to render charts I would need to reimplement helm from scratch including Go templates. Clearly this is not feasible.

This means that to use the functionality of one ecosystem we are locked into that ecosystem.

However, it should all be wasm and interchangeable.

Reactor modules allow us to invoke functions from a module but they do not have a main function or exit.

Utilizing this we could do away with the above limitation.

To continue on the example about rendering helm charts, we could expose that function in a Go compiled reactor module, and a main module from a different ecosystem could call into it provided it was loaded beforehand.

Reactors could be specified as urls or local paths on the cli for takeoff, or provided in the airway definition.

[davidmdm]

Implementations would need conventions around how to pass around memory references and pass through a host function intermediary to load and access from different modules.

Those can be formally defined before work on this is started.