chore: add Github Actions to automate versioning release

[ar3s3ru]

I hate manual tagging because, as everything tasked to a human being, the human factor brings inherent error.

Since we're all ✨ software engineers here ✨ we can automate the tagging process when merging on main -- maybe after the tests have passed?

NOTE: for each feature, a minor release should be used, and fix or minor branch, a patch release should be used instead.

[ar3s3ru]

EDIT: instead of using a continuous deployment style for library releases, the pipeline could:

1. Be created using release/vX.X.X
2. Ensure the version is a correct and valid semantic version
3. Ensure the CHANGELOG.md file is present and up-to-date

Upon merging this branch:

1. A new git tag is released
2. proxy.golang.org is called to force scanning from pkg.go.dev
3. Package and upload a code release on Github Releases