Fix a versioning scheme

[jcp19]

No description provided.

[jcp19]

gobra and gobra-action could have the following version numbering: the major version indicates the year of the release, the minor version indicates the month of the release and the patch version identifies the release in a month.
Every time there is a new release in gobra, a release with the same version number should occur in gobra-action. The changes in the gobra-action release should, at least, update the default imageVersion of gobra in action.yml.

It might be the case that one also wants to create a new release for the action without changing the underlying Gobra release. To address this, one can either allow the patch version of the action and gobra diverge (as long as the patch version of the action is at least the one for gobra). Otherwise, one can wait for a new release of Gobra to also release the changes to the action.

In the future, we could also automate this process.

Any thoughts? @ArquintL

[ArquintL]

To keep things simple, I think I would omit the part that minor versions can diverge. We can simply configure the workflow in Gobra to allow for manual release, which would bump Gobra's minor version in the case we ever need an additional gobra-action release (basically immediately without needing to wait at all for our scheduled workflow to trigger)