Revert "Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608)"

[platinumazure]

This reverts commit 208fb0f.

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain: Revert a breaking change.

What changes did you make? (Give an overview)

Revert PR #9608.

This seems to be the wrong approach to fix #9607: Instead, ESLint errors should render the source text rather than the interpreted string (e.g., "\\b" instead of "\b"), to avoid the need for escaped entities.

Is there anything you'd like reviewers to focus on?

Not really.

[not-an-aardvark]

This seems to be the wrong approach to fix #9607: Instead, ESLint errors should render the source text rather than the interpreted string (e.g., "\b" instead of "\b"), to avoid the need for escaped entities.

This would still be a problem if the source text itself contains control characters, right?

[platinumazure]

This would still be a problem if the source text itself contains control characters, right?

Wait, is that seriously possible? I don't know nearly enough about what characters are allowed in JS files.

In any case, I still think we need to look for a different approach to resolving the original issue. Maybe the XML formatters need to string-replace control characters with placeholder text, to avoid outputting entities.

Do you object to reverting the commit, given at least 2-3 people reported the issue with XML 1.1 incompatibilities? Didn't see the approve, sorry.