[Refactor] Release Process - Steps for a Specific Release

@pljones ci sta già lavorando.

Dal 3/5/2026.

(Tagged for 3.12 but could be done any time.)

**URL**
[Release Process - Steps for a Specific Release](http://jamulus.io/contribute/Release-Process#steps-for-a-specific-release)

**Describe the bug**
Latest version: http://jamuluswebsite.drealm.info/contribute/Release-Process#steps-for-a-specific-release

This probably still needs further work, to be honest. It's referenced as "Tag the release version" [here](http://jamuluswebsite.drealm.info/contribute/Release-Process#release-checklist-for-a-full-release) (and e.g. "Tag a beta release") but covers mostly translations:
> #### 1. Ensure .ts files are up to date (...)
> #### 2. Notify all the translators that translation is required (...)
> #### 3. Update the .ts files returned by translators (...)
> #### 4. When all translations have been submitted and merged. (...) <-- This is where tagging starts
> #### If this is a proper release, move the latest tag (...) (this intended to be a sub-step of 4, I think)

Maybe steps 1-3 should get split into "Translation Process" and step 4 and its sub-step should be "Release Tagging Process"?

Also, the section on updating the ChangeLog would be better placed, in the overall Release Process page, between the section about translations and the section on performing the release -- it needs to happen before the final release and it never gets mentioned in the tagging section(s) (just repeatedly from here, in the places it needs to be).

I also notice this doc doesn't appear to reference the steps in Release Process about the translations.