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

Comienza revisando el README enlazado de CPython WASM y comparando las implementaciones enumeradas: webvm, py2wasm, pyodide y Spin's Python SDK. Define el alcance para un WASM build, una interfaz web básica y el almacenamiento seguro de secrets de proveedores cloud. La implementación y gestión correctas en múltiples clouds son los criterios de finalización.

Escrito por el modelo de indexación a partir del texto del issue.