Can we support cargo run for Ambient projects?

[FredrikNoren]

We might be able to support cargo run in a Ambient project folder; we need to add this to Cargo.toml (for example in the examples):

[target.wasm32-wasi]
runner = "ambient"

To make this work we would also need to make the asset build part of the cargo build. Needs to be experimented with a bit though.

[philpax]

I've been thinking about this more and am starting to think that we should flip the compilation model around so that you can run any arbitrary WASM module, and we remove Rust compilation entirely from the asset pipeline. That is, cargo run builds your WASM, which is then passed as an input to ambient run, and you can do this with any compiler.

The thing that I haven't figured out is how this works with dependencies. When those dependencies have code of their own, what happens? Do we make the user go in and build those manually? Do we enforce that dependencies must have WASM pre-built? What if you don't have the relevant toolchain?