Update release documentation to reflect changes in branching strategy

[marcelovilla]

Context

We are in the process of deprecating the main branch, keeping only develop. We need to update the release documentation to reflect this changes and guide contributors when preparing a new release

Value and/or benefit

We'll have consistent documentation, allowing any interested person to easily understand how to contribute to the release process.

Anything else?

No response