release-notes: document quorum queues default

[jklare]

It was reported that an upgrade from OSISM 8 to OSISM 9 switched all RabbitMQ queues from classic to quorum, and that this is not covered by our release notes.

What changed

The parameter is om_enable_rabbitmq_quorum_queues. It was flipped from false to true in osism/defaults#235 (commit bf60e0f, 2024-10-13), with the matching change in osism/cfg-cookiecutter#674 one minute later. Neither commit carried a release note.

Which release shipped it

Tracing defaults_version from the release manifests against the flag value in each defaults tag:

Release	defaults_version	om_enable_rabbitmq_quorum_queues
8.0.2	v0.20240924.0	false
8.1.0	v0.20250113.0	true
9.0.0	v0.20250407.0	true

So the default first shipped with OSISM 8.1.0, not 9.0.0. Deployments upgrading from 8.0.x to 9 cross it on that hop, which explains the report.

Configuration repositories created before October 2024 do not carry the parameter at all, so they pick up the new default silently. testbed/environments/kolla/configuration.yml still pins false, so CI never exercised the transition.

What this adds

• An Upgrade notes subsection in the 8.1.0 release notes stating that the new default is intended for new clusters, not for upgraded ones, with the recommendation to set the parameter explicitly to false before upgrading to 8.1 or 9. The switch was not tested for 8.1/9 and a migration path was only developed for OSISM 10, so the note points at the RabbitMQ 3 to RabbitMQ 4 migration and makes clear that osism migrate rabbitmq3to4 only exists in OSISM 10.
• A pointer with the same recommendation in the 9.0.0 section, including the config snippet, so it also works for readers who only look at the OSISM 9 release notes.

Verification

• MegaLinter v10 documentation flavor in Docker, markdown linters over all 168 files: clean, no fixes proposed.
• yarn build succeeds with onBrokenLinks: 'throw', so both cross-file anchors resolve.

Not included

docs/concepts/technology-adaptability.md still describes the old approach as "RabbitMQ 3 (classic queues)", which is inaccurate for 8.1/9 defaults. Left out to keep this change focused; happy to fold it in.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ ACTION	actionlint	5		0		0	0.05s
✅ JSON	jsonlint	4		0		0	0.12s
✅ JSON	prettier	4		0		0	0.38s
✅ JSON	v8r	4		0		0	9.58s
✅ MARKDOWN	markdownlint	168		0		0	2.85s
✅ MARKDOWN	markdown-table-formatter	168		0		0	0.37s
✅ REPOSITORY	betterleaks	yes		no		no	0.62s
✅ REPOSITORY	checkov	yes		no		no	18.13s
✅ REPOSITORY	git_diff	yes		no		no	0.08s
✅ REPOSITORY	secretlint	yes		no		no	3.27s
✅ REPOSITORY	trufflehog	yes		no		no	3.63s
✅ SPELL	codespell	178		0		0	0.55s
✅ SPELL	lychee	178		0		0	44.9s
✅ YAML	prettier	6		0		0	0.39s
✅ YAML	v8r	6		0		0	6.53s
✅ YAML	yamllint	6		0		0	0.52s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@10.0.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository