Add a github workflow to automatically generate a new tag

[matheuslc]

What? ⛵

This is a suggestion to automatically create a new tag whenever we push something to main. The tag is based on semantic versioning and will look into the commit message to know if it is a major, minor, or patch.

As we squash commits before merging, we end up with just one commit. The auto-tag will use this commit to know the next version.

For example, our project is at version 1.0.0. A new Pull Request will be merged.
If you add #major to the commit, the next version tag will be 2.0.0
if you add #minor to the commit, the next version tag will be 1.1.0
if you add #patch to the commit, the next version tag will be 1.0.1

Why? 🤔

Checklist ☑️

• I have added added tests for PR or I have justified why this PR doesn't need tests.
• Swager definition added (if new route or route is adjusted)

Links 🌎

PS 🎮

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Matheus Carmo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}