Adds a workflow job to automatically update the version in the code

[clobee]

This PR adds a workflow which does:

Search the code for GCFO_UNDEFINED_VERSION and replaces it with the last release version.

Automatically craft a new tag (according to the commits).
Each merge is a minor version.

For intentional versionning, dev can use magic terms in their commit use: #major, #minor, #patch, #none
The code will then be tagged accordingly .

Search the code for GCFO_UNDEFINED_VERSION and replaces it with the latest tag.
The changed files are being saved in the main branch "main" (the production branch).
A new automated will appear on the branch main changing GCFO_UNDEFINED_VERSION to the latest version.

We recommend dev to use a "develop" branch as a trunk/working branch (the day to day changes).
When devs are ready to publish then they can craft a release using the latest tag(s).

[jojobote]

looks good, how do we make sure this happens at the right time ?
Process should be :

• merge code > autocommit new version in files (using last release + 1 ?) > publish new tag/release

Whereas this looks to do :

• merge code > autocommit current release in files > we need to draft new release with wrong version ?

Let me know if I didnt understand this correctly

[clobee]

@jojobote I have update the description according to the changes made to the workflow. Looking forward to your feedback.Thanks