Test additional code paths in java decoder

[springmeyer]

Currently we do not fully test all these combinations:

• Vectorized path + advanced encodings
• Vectorized path + without advanced encodings
• Non-Vectorized path + advanced encodings
• Non-Vectorized path + without advanced encodings

This PR starts testing all those paths.

The code coverage changes are:

• overall: 36%to 45%
• mlt.converter: 64% to 85%
• mlt.decoder: 55% to 71%

In addition this PR includes:

• Some refactoring in TestUtils.java to share more code between vectorized and non-vectorized
• Improvements to TestUtils.java around geometry comparisons (refs Geometry equality in Java tests #178)
• Improvements to TestUtils.java around property comparisons

Finally, this PR does not attempt to solve any bugs. Rather it finds, isolates, and writes tests harnesses to capture them in code. Once bugs are solved in the future it should be easy to update the tests accordingly.

TODO:

• This PR uncovered a number of bugs that do not have open issues and did not have tests that hit them until now. So I need to create following issues to capture fixing these.
  • Added:
    • Decoding bug: id property is lost #181
    • Decoding error: VectorType not supported yet #182
    • Error in geometry decoding: ArrayIndexOutOfBoundsException #183
    • Incorrect geometry decoding in bing tiles #184
    • Sorting features triggers IndexOutOfBoundsException in vectorized path #185
    • Sorting features causes properties to be non-equal in tests #186
• Property nesting in MLT makes comparison to MVT difficult so I disabled it in this test refactor because comparison to MVT is what the decoder tests rely on. My sense is that standalone unit tests of nesting might be more appropriate than including nesting in the decoder tests. Do others agree?

[msbarry]

Looks good! A few minor comments TIOLI

[springmeyer]

Looks good! A few minor comments TIOLI

Thanks @msbarry! Replied to your comments. I'll merge this shortly.

[springmeyer]

As intended & expected, this failed after pulling in #184:

MltDecoderTest > Decode Bing Tiles > com.mlt.decoder.MltDecoderTest.decodeBingTiles(String)[1] FAILED
    org.opentest4j.AssertionFailedError: Error for 4-8-5/non-advanced: 0 ==> expected: <2> but was: <0>
        at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
        at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
        at app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
        at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
        at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:563)
        at app//com.mlt.decoder.MltDecoderTest.decodeBingTiles(MltDecoderTest.java:70)

Which is fixed by updating the test expectation in 7123203