Documentation / Unify version numbers in doing a release page

[josegar74]

Follow up of #7412 with updates to unify the release versions used in the different sections of Doing a release page, identified while backporting #7412 to 4.2.xbranch.

This PR is only for main branch, should not be backported.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[jodygarnett]

All the changes made look good - however I expect we need to play test this procedure (by making a release) before these instructions can be trusted.

Can we try this procedure as written, and make a PR during the release process correcting anything that did not work.