Finalize release notes for v9.1.1 release

[elasticsearchmachine]

This PR was auto-generated. Please merge after approval. cc @elastic/es-delivery

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[github-actions]

🔍 Preview links for changed docs

• docs/release-notes/breaking-changes.md
• docs/release-notes/deprecations.md
• docs/release-notes/index.md

[eedugon]

LGTM

[eedugon]

@charlotte-hoblik : I'm a bit lost with this PR..... wasn't #132488 suppose to do the same?

I have approved this, but maybe this shouldn't be merged.

cc: @elastic/es-delivery & @shainaraskas

[charlotte-hoblik]

Thanks for bringing this up @eedugon I can absolutely see why this might be confusing.

@yetanothertw and I are working on a POC to rewrite the Elasticsearch release notes into a new format, based on the excellent guide she and Aleksandra created. As part of this process, we’re manually rewriting the notes into the new format.

The reason you saw so many changes compared to the release notes PR is that this finalizing PR essentially overwrote the manual updates from the earlier PR when you first reviewed it (back to the original layout). I’ve since merged a commit restoring those editorial changes, so the “amount of change” is now back to normal.

We also have an internal ticket for this sprint to slightly adjust the release note process for Elasticsearch: https://github.com/elastic/developer-docs-team/issues/334. Specifically, we’ll remove the coming tag so finalizing PRs don’t undo earlier edits.