feat(encoding): added XML parser

[JuanM04]

To-do:

• Implement parser
  • Add multiple outputs
  • Add tests
• Implement stringify
  • Add tests
  • Support multiple inputs (?)
• Added escape utility

[CLAassistant]

All committers have signed the CLA.

[kitsonk]

This is a lot of work. Has there been a conversation with a core team member about this being a good contribution to deno_std? If so, it would be great to link to it or an issue where conversation has gone on.

[JuanM04]

I did not have any conversation about this. I was experimenting with XML and, since Deno has support for YAML, TOML, CSV, and other common formats, I thought it would be a nice addition. If you don't think it should be integrated in deno_std, I could easily extract it into its own package

[kt3k]

Is it possible to make this compatible with DOMParser API?

[andreubotella]

Note that @b-fuze is independently thinking of adding integration with the XML parser xml5_ever in their deno_dom library (as per a conversation on the Deno discord).

[kitsonk]

Having XML parser as part of deno_dom would be a lot better in my opinion. YAML, TOML, CSV are far more simplistic of parsers than XML.

[cjihrig]

This has been idle for a few months. @kitsonk @kt3k do we want to move forward with this? If not, can we close it out?

[kt3k]

I'm in favor of closing this one for now.

I agree with @kitsonk . I think we should have xml parser as part of DOM API instead of invented API.