Allow repacking templates of different compatible versions

[destijl]

If you have 3.1.0.2 installed the repacker only looks for 3.1.0.2 templates, which is unnecessarily constrained since we support 3.1.* templates talking to the 3.1.* server.

Add a way to override this behavior.

[destijl]

More difficult than I thought:

can't just glob for available templates, or provide a --version option to config_updater because you then need to parse out what version you have, and change it everywhere: output filenames, pyinstaller metadata, deb package metadata etc. it's crazy complicated.

we could provide a --version option that just sets major minor etc. in the config system for the duration of the config_updater run, but we'd have to be careful to set the old values back. This is a fair bit of messing around that is equivalent to changing the version in .local.yaml running config updater, and then putting it back.

If you want to repack a different version I think the procedure is:

pip install the packages
copy your config over
change version to the one you want to repack
run config_updater to repack

that way you don't have to mess with your prod server config.

So I think we just continue to support the single template version for repacking. We need to release the templates before the server, so they should always be available.

[destijl]

Reopening, since punting on this has created a problem:

If you need to update the client, you essentially have to also make a server release. Otherwise the latest templates can't be easily repacked by the latest server. Being forced to make a server release for a potentially minor client fix is not good. Since the components are part of the client package it's even worse: a server release every time you want to update a component. That's not workable.

What makes this hard is that we treat repacking like building and use the version number from the current config in lots of places. What we should really do is get the version number from the client template when repacking, so a 3.1.0.5 template repacked by a 3.1.0.2 server will be version 3.1.0.5.

We could split components into a separate repo, but this adds packaging overhead and there is already too much. Since all this saves you is copying templates from the previous release I don't think it's worth it.