Templates that depend on plugins that have to match SDKs that get referenced in templates, oh my

[itowlson]

Each version of the JavaScript templates references a particular version of the JavaScript SDK NPM package. Each version of the NPM package requires a certain minimum version of the js2wasm plugin. This is quite a few moving parts to keep in sync. For JS and Python, the Fermyon installer brings everything up to the same level, but it would be good to have a general purpose strategy that non-Fermyon languages can use. This is not immediate, but is something to bear in mind for a future iteration of the templates subsystem.

[mikkelhegn]

Let me know if you think this is it's own issue, but having template version compatibility with Spin being tied to GH tags, seems sub-optimal, as users use the main branch of repos to look at examples, and that may not match the version of a given template, which are using.

One suggestion could be to have the template system itself support multiple version of a template within a template (the directory).