Improve clarity and structure of release notes

[Maren-SSB]

Originally opened by Kristin in Jira, March 2026.

Det blir flere og flere brukere/organisasjoner som følger med på PxWeb 2 sine release-notes, og fint om de kan grupperes etter endringstype, så de blir enklere å forstå for de som følger med fra sidelinjen.

Mimir har et godt forslag på hvordan en release-notes kan være: https://github.com/statisticsnorway/mimir/releases

[runejo]

I have set up release please It's the same product as mimir uses.

See my fork for an example https://github.com/runejo/PxWeb2/releases/tag/v2.9.0

The associated PR will aslo make it possible to enable immutable releases #114

The only missing feature in this PR is the ability to make pre-releses (beta, rc, ...)

[runejo]

I think we should require linear history in all our repos

• https://github.com/googleapis/release-please#linear-git-commit-history-use-squash-merge
• https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-linear-history

[runejo]

The only missing feature in this PR is the ability to make pre-releses (beta, rc, ...)

If you run the workflow manually, you can now force a pre-release, the first one will append -rc.1 if you release another it will be -rc.2