Update release issue template to reflect branching strategy changes

[marcelovilla]

Context

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

Value and/or benefit

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

Anything else?

No response

[viniciusdc]

Also, I wonder, do we need the upgrade command to be present for an RC? -- To me, it does not make sense as we need to pin the version in the class anyways, so this looks like a final release thing to me.

[marcelovilla]

Closing this as it was handled in 0470a01