Use safer XML escaping

[jkrems]

Description of the Change

Fixes a regression introduced in #2957. It was too aggressive in its use of named escapes which broke XML files that might not support all of the named escapes available in HTML.

Alternate Designs

We could try to get support for safe named escapes into he. But given that this won't affect the visible output, I focussed on fixing the functionality first.

Why should this be in core?

Benefits

Possible Drawbacks

This makes the HTML output a bit uglier. E.g. it won't use the nice " anymore.

Applicable issues

[coveralls]

Coverage increased (+0.04%) to 89.072% when pulling 8e50351 on jkrems:jk-xml-encoding into 72622ab on mochajs:master.

[boneskull]

thanks

[JamesMGreene]

Thanks for the quick turnaround here, @jkrems and @boneskull. 👍

This was making hundreds of our CI builds fail today. 😵

[jkrems]

@JamesMGreene Sorry for that & thanks for the report! :)

[JamesMGreene]

@boneskull Could you kindly drop a comment here when v3.5.3 is published to NPM? Thanks!

[boneskull]

published as v3.5.3

[arwilczek90]

Thank you so much! That threw me for a loop all morning!