Fix release management

[abelsoares]

I think the way this repo is setup is hard to manage it using tags.
Every time we makes changes to workflows or add new workflows, if we want to use tags in client workflows, we need to create a tag. The problem is that the tag impacts the whole repo, meaning that a stable workflow can have many tags but the code is the same. This is misleading.

An alternative would be to maintain a repo per workflow, but i like the idea of having a centralized repository.

Maybe we should agree on follow the github suggestion of using the commit SHA: https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows#calling-a-reusable-workflow

[franciscomorais]

For me sounds good but, creating a tag wont prevent you from using a hash. Lets just say we can simply use both.

That is, for stable versions, we can create a tag, but for workflows that are still in development or testing, we can use hashes.

There are many methods, including creating a custom tag that can be recreated each time you want to update the tag code. This is useful while we're developing.