Sim4Life-Web dy-service versioning

[SCA-ZMT]

Conclusions from the working group

• [x] All s4l-based services get identical version numbers
  • sim4life
  • isolve
  • JupyterLab
  • python runner
• [x] For now, version numbers will be 8.0.0, 8.0.1, 8.0.2. This requires the Desktop Versioning to be changed because the web will release more often
• [x] The services will be named sim4life 8.0 (next minor release sim4life 8.2) and user will be able to select patch versions
• [x] We will buffer the latest official desktop version and the latest patch
• [ ] The Dashboard in the services tab will show all versions similar to the Tutorials in a list with headers: 8.0. 8.2, 9.0
• [x] Since the service key will change from 8.0 to 8.2 we need to improve the updating mechanism in the frontend (first example will be moving from current lite to lite 8.0)

---

### Tasks
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/6201
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/2521
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/6456

### Eisbock
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1419
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1420
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5476
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/6202
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1704

### Tom Bombadil
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5964
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1426
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/6068

### Leeroy Jenkins
- [ ] https://github.com/ITISFoundation/cookiecutter-osparc-service/pull/113
- [ ] https://github.com/ITISFoundation/osparc-simcore/pull/5902
- [ ] https://github.com/ITISFoundation/osparc-simcore/pull/5913

[mguidon]

After discussion with @eofli, we do not need to group the services by version. They can all got into one service. That reduces the problem to making services compatible among minor and major versions and among service keys.

[drniiken]

As discussed in the pre-planning, we need a good "DEFINITION OF DONE" for this case. We/Team can maybe have a chat later this week or next week. Thx, best, Nik

[pcrespov]

[mguidon]

As discussed, merging of the tiles will not be done programatically but through retagging/labeling of the corresponding (entrypoint-) images. This requires:

• Retag all isolve, jupyter-smash, s4l-python-runners and sim4life master services that are listed in the registry-syncer config (lets first check if tag and "key" label is enough (I dont think we need the "compose-spec" as well)
• Update the list of images to sync
• For all key:version pairs above copy all entries in the following tables:
  • resource_tracker_pricing_plan_to_service
  • services_access_rights
  • services_specifications
  • services_vendor_secrets
  • `user_preferences_user_service (I think this one can safely be omitted)
• Finally, update the following table:
  • services_compatibility

@pcrespov I guess the db part is trivial to script once we are sure the list above is complete?