Remove extension from version.json files and make actions pick the extension digit automatically

[jrobinAV]

Description

Keeping the extension in the version.json files does not bring value. A developer who wants to create a dev release does not care which number it is.

This issue has two goals.

1. It aims to remove the extension in all the version.json files and keep the next version number targeted.
2. It also aims to make the build and release processes automatically pick the correct dev version to build based on the versions already created.

Example

Let's assume the last stable versions are the following:

• taipy-common-X.Y.Z
• taipy-gui-X.Y.Z+1
• taipy-core-X.Y.Z+2
• taipy-rest-X.Y.Z
• taipy-templates-X.Y.Z
• taipy-X.Y.Z+3

develop branch

On the develop branch, the version.json files should contain X.Y+1.0 for all packages (taipy, common, gui, core, rest, template)

release branch

On the release/X.Y branch, the version.json files should contain the following:

• taipy-common: X.Y.Z+1
• taipy-gui: X.Y.Z+2
• taipy-core: X.Y.Z+3
• taipy-rest: X.Y.Z+1
• taipy-templates: X.Y.Z+1
• taipy: X.Y.Z+4

Release single package workflow

After releasing a production version, let's say X.Y.Z (from branch release/X.Y), the version.json of the released package in the release/X.Y branch should now contain X.Y.Z+1. The other packages should not be changed.

When releasing a dev version to prepare release X.Y.Z, the workflow should automatically find the latest dev version of the X.Y.Z. Let's say the latest dev release was X.Y.Z.devA.
Then the workflow should build the X.Y.Z.devA+1. Once it is built. There is nothing to update in the version.json files on any branch.

Release all packages workflow

After releasing a production version, let's say X.Y.0 (from branch release/X.Y), all the version.json in the release/X.Y branch should now contain X.Y.1.
All the version.json in the develop branch should now contain X.Y+1.0.

When releasing a dev version to prepare release X.Y.0, the workflow should automatically find the latest dev version of the X.Y.0. Let's say the latest dev release was X.Y.0.devA. Then the workflow should build the X.Y.Z.devA+1. Once it is built. There is nothing to update in the version.json files on any branch.

[github-actions]

This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines.