Latest version of @typeberry/pvm always available.

[tomusdrw]

Currently every time we change something in typeberry PVM we need to publish a new version to npm and then create a PR and update the code in pvm-debugger.
It would be cool to figure out how to shorten that release-cycle to always have up-to-date typeberry PVM.

The idea is to maybe have something similar to other PVMs, where the latest version is fetched from some URL?

• However the challenge is to load a JS code from an external domain (cross-origin issues)?
• Can we fetch the JS code using <script tag?
• Can we fetch the JS as text and then eval?
• Is there some other option?

Alternatively we can setup and auto-update workflow if a new version is detected at npm.

[tomusdrw]

Probably makes sense to unify and clean up all PVMs API, so that all WASM pvms and npm-based @typeberry and script-loaded @typeberry has the same API.