Replace JSON11-produced hex escape codes with unicode escape codes

[wjordan]

Description

Since #784, JSON11.stringify produces JSON5 documents with hex escape codes (\x1b), which aren't standard JSON and cause JSON.parse to error. When using JSON11 code path, this PR applies a fix to replace all \xXX escape codes with the JSON-compatible equivalent Unicode escape codes (\u00XX).

This PR adds a unit test verifying the fix by ensuring a round-trip s.deserialize(s.serialize(obj)) with an object containing long numerals and ANSI escape sequences completes successfully without error.

Issues Resolved

Fixes opensearch-project/OpenSearch-Dashboards#7367.

Check List

• New functionality includes testing.
  • All tests pass
• Linter check was successfull - yarn run lint doesn't show any errors
• Commits are signed per the DCO using --signoff
• Changelog was updated.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[nhtruong]

Thanks @wjordan
Do you think this is a bug in JSON11 library?
Don't forget to update the CHANGELOG.md file.

[wjordan]

Do you think this is a bug in JSON11 library?

No, the json11 library writes JSON5 documents as expected, the bug is in the serialization code in this repo. See the added unit test which fails without this PR.

A feature request for json11 to take an option to stringify that would return JSON-compatible strings (instead of JSON5) would be another way to solve this issue instead of doing a regex replace here, but I wouldn't call the lack of such an option a bug.

[AMoo-Miki]

Ideally, this should be handled on JSON11. I will find how that is happening.

Update: JSON11 v2.0.0 was published with a change in behavior.

@wjordan can u try bumping JSON11 to 2, without the changes in this PR to see if it solves it for you?

[ycyr]

any update ?

[nhtruong]

I'll take a look at this and try @AMoo-Miki 's suggestion.

[nhtruong]

looks like JSON11 2.0 has already resolved this issue. Both 2.13.0 and 3.x are using JSON11 2.0. @ycyr are you having trouble with this? would you mind opening a ticket describing what's happening on your end?

[ycyr]

@nhtruong I've just upgrade my cluster to the version 2.18 (I was at the version 2.16) and the problem has been fixed.

[nhtruong]

Closing this since this has already been resolved by JSON11 2.x