Add a breaking change note for non-detailed errors

[thecoop]

#90529 (comment) - add a release note about the change

[github-actions]

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

[elasticsearchmachine]

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

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[mosche]

lgtm, but won't this be lost in case docs are re-generated?

[thecoop]

This is where the breaking changes are recorded. I don't know what's going to happen with the change to md, but if it's alongside all the other release notes then it's in the right place now.

[brianseeders]

@thecoop, @mosche is right. There needs to be a change in docs/changelog/90529.yaml for this. The asciidoc that you modified gets auto-generated from the yaml files, so your change will get blown away.

[leemthompo]

These files are being migrated to Markdown, and any changes merged now will be lost.

The warning is not lying 😄. No asciidoc pages are being published anymore for 9.0/main so this PR will have no effect. There shouldn't even be any asciidoc files on the 9.0 branch TBH.

FYI we shouldn't be editing any asciidoc on any version branch higher than 8.x, and as Brian mentioned the changelog yaml file will ensure this change gets picked up when the release notes are being generated.

[rjernst]

There shouldn't even be any asciidoc files on the 9.0 branch TBH.

I opened #126120 to address that.