Bugfix: NullPointerException thrown for invalid input on JSONTokener without strict mode

[Simulant87]

expect input to be parsed as the invalid characters are at the end after a valid object, but got a NullPointerException instead, providing a fix with null checks.

fixing #933

[stleary]

What if JSONTokener had a default JSONParserConfiguration?

[Simulant87]

What if JSONTokener had a default JSONParserConfiguration?

That would also fix the NullPointerExceptio, if the JSONTokener would be initiated with a default JSONParserConfiguration.

However, the JSONParserConfiguration is not passed in the constructor and is not final. it can be changed by the setter after creation of the JSONTokener, which could also set it to null. In the case of passing null to the setter, it should then also create a new default JSONParserConfiguration.

[stleary]

@Simulant87 The new unit tests can be kept after #937 is merged, but I believe the code in JSONObject and JSONArray will no longer be needed. But let me know if you disagree.

[Simulant87]

I agree, the null checks would no be longer necessary. I integrated everything in #938 which validates it.

[Simulant87]

this PR should be closed in favour of #938 (when that one is merged).

[stleary]

Closing this PR as the work is being done in other tickets