Review how to manage the plugin version: major.minor.patch

[cmoulliard]

TODO

As our plugins are now part of the backstage-playground project, we should handle them like backstage do according to the following rules:

• When we release a plugin we follow the convention Major.Minor.Patch
• Post release, the number should be incremented to: Major.Minor.Patch+1-next. I dont think that we should like backstage suffix it with *-next.[0....n].
• The dependencies of the backstage application (= packages/app and packages/backend) should point to the workspace like this "@backstage/plugin-kubernetes-backend": "workspace:^", to avoid to use released packages and to debug/code changes. Note: Such a change means also that when a PR will build an image, the plugin's code of the PR will become then part of the new image created. We should perhaps like janus-idp create an image suffixed with the name of the PR like pr-1122 etc

Backstage example:

{
  "name": "@backstage/plugin-app-backend",
  "description": "A Backstage backend plugin that serves the Backstage frontend app",
  "version": "0.3.67",

and

{
  "name": "@backstage/plugin-app-backend",
  "description": "A Backstage backend plugin that serves the Backstage frontend app",
  "version": "0.3.68-next.0",

[cmoulliard]

The version of a plugin can be increased using the semver tool (https://www.npmjs.com/package/semver) and this command

semver 0.1.28 -i prerelease --preid next -n 0
0.1.29-next.0