IDEA: WASM build to deploy-to & manage different clouds without a separate Python server

## Feature Request

Aside from a basic web interface, the main thing this would need is a way of setting and storing secrets (like cloud provider auth keys).

As for official CPython support see: https://github.com/python/cpython/blob/main/Tools/wasm/README.md

Now there are plenty of unofficial implementations that don't have those same limitations, for example: [cheerpx webvm](https://github.com/leaningtech/webvm); [py2wasm](https://github.com/wasmerio/py2wasm); [pyodide](https://github.com/pyodide/pyodide); [spin](https://github.com/spinframework/spin-python-sdk)+CPython official approach

Advantage:
- Multicloud management without user installing anything
- Facilitate one-click install use-cases onto multiple cloud vendors
- Many others

Start by reviewing the linked CPython WASM README and comparing the listed implementations: webvm, py2wasm, pyodide, and Spin's Python SDK. Define the scope for a WASM build, basic web interface, and secure cloud-provider secret storage, with successful multicloud deployment and management as the completion criteria.

Written by the indexing model from the issue text.