Json-schema validator custom reporters that can control json-patches and other thing

[Oplkill]

Add to the Json-schema validator custom reporters:

1. json-patches - allows users to take action on an error by providing a Json Patch
2. error type (enum class) indicates the exact type of error that occurred, making it easy to identify what happened.
3. optional<Json> objInfo1/2/3 - contain contextual information about the error. For example, for an error like "Wrong field type XXX", where objInfo1 will be "field name", objInfo2 - "expected type name", objInfo3 - "current type name". It will depend fully on the (2) error type enum-class. (of course docs will tell about it)
4. json_schema_fragment - the specific part of the Json Schema where the problem occurred.
5. report->SetError(false/true); - to be able mark that problem as not an error
6. Replaceable error text - allows the user to customize the error message, for example, to translate it into another language
7. validating object json path - shows the path within the object being validated where the problem occurred
8. json schema path - for showing path to the checking part of the schema

That idea allows users to do such thing:

1. Translate errors
2. Ignore not essential errors
3. Make json-patches in custom report that will fix validating object(but of course patch will not be applied immediately(same as now, lib just return patch), user will be needed to validate again to be sure that is patched object is still valid)

Raw execution of that idea: #677

[Oplkill]

Lets view that Json schema:

{
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "type": "object",
    "properties": {
        "name": {
            "type": "string"
        },
        "is_edible": {
            "type": "integer",
            "default": 0
        },
        "contains": {
            "type": "string",
            "default": "Nutritions"
        }
    },
    "required": [
        "name",
        "is_edible"
    ]
}

And that Json that will be validated against schema

{
	"name": "Chair",
    "is_edible": false
}

Normally validator will say that "Invalid type. Expected Integer but got Boolean.", but user of the lib could wanted to fix that Json.
With custom reporter that will convert all convertable values(like int<->boolean) and mark those things as not error.
And currently validator will add to patch "contains": "Nutritions", but user could didn't wanted it. Why? Because that field wasn't required by schema. Like the idea "add only those fields that required by schema but not exists and have default value" With custom reporter user could do this

[danielaparker]

Thanks.

Regarding error translation, long term I'd like to move away from error messages hard coded in C++ source code to parameterized messages in resource files, like networknt/json-schema-validator does with message properties.

I like the idea of supporting user augmented json patches in custom reporters to fix the validating object.