Compile an actor code to WASM in a ready-to-go bundle with metadata to deploy to the backend

[boorich]

Is your feature request related to a problem? Please describe. Please describe the problem you are trying to solve.

Describe the solution you'd like Please describe the desired behavior.

Describe alternatives you've considered Please describe alternative solutions or features you have considered.

[LesnyRumcajs]

Note on the metadata - we would like to avoid using hashes, CIDs and addresses during development as much as possible. Like in docker, every container has a hash but it also has a human-readable name.

Thus, each bundle would have:

• release WASM bundle,
• debug WASM bundle,
• the metadata in an agreed format (e.g., toml), separate for debug and release as CIDs change:
  • actor name to CID mapping,
  • method name to method number mapping,
  • labels (e.g., debug),
  • anything else that might be useful (e.g., I could imagine someone adding version support)
  • source code? It might be helpful; I can think of a few practical applications if we store this, especially if it is remote.

The bundle will be packed into a tarball, ready to be ingested by the backend into the Actor Store.