Update release steps

[offtherailz]

Description

This PR improve the release procedure to:

• explicitly ask to merge the update release
• add a point to restore the snapshot version of GeoStore.
• Updated links to readthedocs, that now has a new dashboard and the old links will be dismissed in early 2025

This list have to be improved a little bit, so it is in draft

Note:

There are 2 ways of keeping mapstore and geostore aligned: 1.release geostore more frequently and before the mapstore release, changing the fixed version when ready 2- using the -SNAPSHOT version on release branch, until we effectively use it.

• Solution 1 makes things more stable, but need alignments and the geostore versions in the middle will not be tested
• Solution 2 is more unstable, but guarantees a continuous testing until the release.

For this reason we are going to choose the 2nd strategy.

Please check if the PR fulfills these requirements

• [x] The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• [ ] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [x] Other... Please describe:

Issue

What is the current behavior?

10645

What is the new behavior?

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• [ ] Yes, and I documented them in migration notes
• [x] No

Other useful information