Encoding of JSON file contains unicode representation instead of symbol

Relations

Possible related to issues: #464 & #740

Issue

Inputs

Currently, having simple JSON file, like (test.json):

{
    "TestValue": "test <test@test.test>",
    "TestValue2": "&",
    "TestValue3": "@"
}

Using the .sops.yaml file with KMS defined and command:

sops -e -i test.json

And decrypt:

sops -d --input-type=json -i test.json

Results

After decrypting the input file doesn't decode all symbols, like (this is founds only, might be more):

• & Unicode Character 'AMPERSAND' (U+0026)
• < Unicode Character 'LESS-THAN SIGN' (U+003C)
• > Unicode Character 'GREATER-THAN SIGN' (U+003E)

and result is the following:

{
    "TestValue": "test \u003ctest@test.test\u003e",
    "TestValue2": "\u0026",
    "TestValue3": "@"
}

It might be a huge issue, while the example in the first value should represent the proper email info, like:
User Name <user@example.org> instead of User Name \u003cuser@example.org\u003e.

Environment

• SOPS version: sops 3.7.1 (latest)
• Cloud: AWS / KMS
• OS: MacOS Big Sur (11.3.1)

Expected results

The JSON values should be decoded in the same manner for all symbols to avoid data discrepancy.

Reproduce the behavior with test.json and the .sops.yaml KMS configuration using the documented sops -e and sops -d commands, then trace the JSON input/output path from those CLI entry points. Done means encryption and decryption preserve literal &, <, and > in the shown values, with coverage for the expected JSON output.