docs: add full GitHub release history to release notes (#1280)

Add a Release History chapter to the Release Notes guide with the full
descriptions of all 69 published GitHub releases, from 4.0.1 through
5.2.0, their publication dates in UTC, and links to the original release
records. Connect the chapter to the guide index, Antora navigation and
PDF, and link the existing 5.2.0 summary to its full notes.

Use the release Markdown as the text source, preserving change lists,
contributor credits, supporter content and command placeholders. Keep
`@Override` and `@param` literal, escape bot-name brackets, and preserve
three literal dots in comparison URLs and all 34 commit-only
descriptions. Link 288 issue references and all 34 commit-only ranges
without changing their displayed text. Honor explicit repository
qualifiers such as `OpenIdentityPlatform/OpenAM#980`, and keep `PKCS#1`
as a cryptographic term. Normalize the hyphens in `CVE-2025-12194` to
ASCII so the identifier remains searchable and copyable.

Use Asciidoctor PDF's bundled `default-with-font-fallbacks` theme to
display supporter emoji. Preserve the original heart presentation
selector in HTML and omit it only in PDF, where the bundled fonts cannot
display it. Render supporter graphics as links in PDF. Document snapshot
maintenance and that only explicit `history-X-Y-Z` release anchors are
stable; generated subsection IDs can shift when releases are prepended.

Extend `AntoraPageTitlesIT` to cover the new page's document title and
fragments, all three Release Notes chapters, literal Java tokens and the
CLI placeholder, representative comparison ranges, issue links with
grouped references and repository qualifiers, and the searchable CVE
identifier.

Validation:
- Ran all three documentation test classes directly with TestNG and
AsciidoctorJ 2.5.11 against output generated by doc-maven-plugin 3.2.2:
36 tests passed, including all 10 `AntoraPageTitlesIT` cases.
- Confirmed that eight intentional mutations fail the regression checks:
bare three-dot ranges, unrelated account links for each Java token, a
deleted Java token, the missing CLI placeholder, an unlinked issue, an
incorrect repository qualifier and Unicode CVE hyphens. An unrelated
prose ellipsis remains allowed. Restored the generated page and
confirmed that the checks pass.
- Compared the complete rendered history text with the existing
snapshot: visible text is preserved apart from the deliberate CVE hyphen
normalization. Verified all 34 new comparison targets through the GitHub
API. Permanent assertions cover three representative range forms; this
validation additionally checks all 34 ranges.
- Checked 33 file cross-references across the seven Release Notes and
Getting Started source pages; `git diff --check` passed.
- Built preprocessing, Antora modules and both guide PDFs with
doc-maven-plugin 3.2.2 using a standalone validation POM. The 53-page
Release Notes PDF contains all 69 release headings, all 34 literal
commit ranges, both Java tokens, the CLI placeholder and the normalized
CVE identifier. Verified the new issue/compare destinations in actual
PDF URI annotations.
- Confirmed that NotoEmoji is embedded, inspected the rendered supporter
emoji, and checked that the PDF build reports no missing-character
warnings.

The full reactor remains unverified locally because offline project
loading requires the uncached `central-publishing-maven-plugin:0.12.0`;
this revision still needs full CI verification. The bundled PDF renderer
displays folded hands correctly but writes an invalid
supplementary-character ToUnicode mapping, so extracting or copying that
decorative emoji from PDF can return a different character. HTML
preserves the original emoji.