Support seperate versions for each module.

[matifali]

We need to bump the version for all modules or do some parsing to detect which modules have changed between tags.

It would be ideal if each module could have its versioning instead of the repo version tag.

@mafredri has some interesting ideas here.

[matifali]

After discussing with @mafredri, we can have tags like module-name/1.0.0

A similar release tagging is seen on moby/buildkit repo.

[matifali]

@mafredri We now have versioning supported in the backend, and each module, if tagged with module-name/version, will have its own version.
I can use some help in updating the CI and ./update-version.sh script.

[matifali]

@bcpeinhardt We need to update versions checking logic for PRs for example #407.

Then we can push a tag, let's say jupyterlab-v1.0.24, and as part of the release workflow, update the README.md version to v1.0.24 (extracted from pushed tag)

See