2.7.0 SUPPRESS_EXCEPTIONS not backwards compatible with 2.6.0

[Bonnev]

In addition to #840 the following code works fine (no errors) on 2.6.0 but throws an exception on 2.7.0:

Object value = JsonPath
	.using(Configuration.defaultConfiguration()
		.setOptions(Option.SUPPRESS_EXCEPTIONS, Option.DEFAULT_PATH_LEAF_TO_NULL))
	.parse("{\"random\":{\"test1\": 4}, \"mandom\":{\"test2\": 10}}")
	.read("$..test.max()");
System.out.println(value);

[marchof]

Looks like this was broken in this PR #775.

[5Orange]

Same #908

[mpassell]

@kallestenflo I just hit this issue as well when trying to upgrade from v2.6.0 to v2.7.0+ (v2.9.0, to be specific). Based on how JsonPath.handleMissingPathInContext() was implemented, it can cause a different type to be returned by JsonPath.put(), which then causes a ClassCastException in JsonContext.put(). Based on that, I don't see how I can restore the behavior I had in v2.6.0 no matter which Options I enable.

I think that the changes in #871 would fix this for me if you could merge that. If not, but there was a way to make a v2.6.1 with the vulnerability fix in v2.9.0, that would be great.

Edit: If I were to cherry-pick the commit(s) from #985 and create a PR against the 2.6.0 tag/branch, would that be helpful?