Auto release workflow

[sebastian-quintero]

Description

This PR modifies the release workflow to be automatic. Now we keep two types of versions:

• The app version: the version used to nextmv community clone the app.
• The marketplace version: the version used for the marketplace.

The app version is auto-updated based on today’s date and a counter. If the app is release more than once a day, the counter simply increases.

The marketplace version is auto-updated by bumping the minor version. There is a new filed in the workflow-configuration.yml file called marketplace_major_version. If that version is changed from v1 to v2, for example, the auto-release workflow will now start updating from v2.0.0 onwards. That is the place where one would specify a new major version being released. If that field is not updated, we will always do a minor bump.

There is a new .nextmv/release folder because the logic started to get complex, so the release script is now a package with multiple files. The main file is .nextmv/release/main.py.

The release.yml workflow was modified to pick up changes on the community apps and do an auto-release.

[merschformann]

Will the manual part of this workflow stay? When releasing manually, we should probably not bump the version, right?
I.e., if we run against dev/staging, we don't want to mess with the version of the app in the repo, but rather just push it there, right? 🤔

[sebastian-quintero]

I left the manual dispatch in case we needed to release by hand (although we shouldn't need to). In any case, the inputs are just names, the version is not specified anymore, in neither the manual nor the automated way.

[merschformann]

Nice! 🎉
Just a remark about potentially skipping version bumps on other environments than prod, just to ensure that there will be no confusion with versions missing from prod (but being in code).