Fix array predicates in JSON path filters

[kwvanderlinde]

Identify the Bug or Feature request

Fixes #3358

Description of the Change

We now use GSON as the mapping provider in addition to the JSON provider when using JsonPath. This allows array values to be built by JsonPath, where before it was unable to instantiate List.

The only remaining non-GSON representation is JSONSmart, used by JsonPath to parse literals in the path expression. This is hardcoded, and unfortunately results in some inconsistencies noted below.

I also included some cleanup to eliminate JsonParser instances, as those are deprecated and we don't need them anyways.

Possible Drawbacks

There will no doubt be some confusion over the exact behaviour of array predicates. Most predicates should just work as expected (e.g., anyof, equality between numbers, etc), but specifically equality checks on numeric arrays are a problematic case that I don't think we can just fix. Such predicates will require the integral literals to be written with a decimal point so that JSONSmart treats them as doubles to match what the GSON mapping provider produces for the other operand. Using integers, the predicate will never match.

Documentation Notes

Given this data set:

[h: data = json.append("[]",
	json.set("{}","key",1,"array",json.append("",2,3)),
	json.set("{}","key",2,"array",json.append("",1,2,3))
)]

The following expressions will work to filter an array:

[r: json.path.read(data, "\$[?(@.array == [2.0, 3.0])]")]
[r: json.path.read(data, "\$[?(@.key in [2,3])]")]
[r: json.path.read(data, "\$[?(@.key == 1)]")]
[r: json.path.read(data, "\$[?(@.key == 1.0)]")]
[r: json.path.read(data, "\$[?(@.array anyof [2,3])]")]
[r: json.path.read(data, "\$[?(@.array anyof [2.0,3.0])]")]

But this one will not match any elements since the integers inside the array are not considered equal to the floats used internally for the array being matched:

[r: json.path.read(data, "\$[?(@.array == [2, 3])]")]

Release Notes

• Fixed json.path functions so that array predicates can be used.

---

This change is