ci(release): use new branch naming strategy

[smoya]

Relates to #734 (comment)

This PR changes the .releaserc file to reflect the changes on the branch naming strategy for releasing; using next-spec and next-major-spec branches.
This PR also updates the RELEASE_PROCESS.md accordingly. It also removes the step where the Release Coordinator should ask the Code Owners to create the release branch + the step where those should be added into .releaserc and/or package.json as they are not needed anymore.

[dalelane]

love how this made the process shorter :-)

[fmvilas]

Just some minor (no pun intended) suggestion

[dalelane]

LGTM

[smoya]

/rtm

[asyncapi-bot]

Hello, @smoya! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: Add a comment to your PR with the text: /au or /autoupdate and our bot will take care of updating the branch in the future. The only requirement for this to work is to enable Allow edits from maintainers option in your PR.
Thanks 😄

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[smoya]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-major-spec.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[fmvilas]

Forget about the last comment saying it was released in version 2.5.0-next-major-spec.1. I made a mistake and it created this version but it should actually be 3.0.0-next-major-spec.1. There's a notice in the release. Apologies for the noise.

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-spec.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[derberg]

Recent comments about the release from the bot were added by mistake. More details in #899