The WMTS test suite tests invalid I/J values, documents it looks for InvalidParameterValue, actually checks for TileOutOfRange, while the standard wants PointIJOutOfRange

[aaime]

Describe the bug
When a GetFeatureInfo is performed using an out of range I or J value, the ATS states:

Test method: When a request contains an I or J greater or equal to TileHeight and
TileWidth respectively for the selected TileMatrix, then the server throws an
exception (code=PointIJOutOfRange) in Procedure Oriented Architectural Style or a
HTTP 404 File not found in Resource Oriented Architectural Style

PointIJOutOfRange is also described in Table 26 (page 48), as part of the "Exception codes for GetFeatureInfo operation".

However, the test documentation, displayed in the final report, checks for:

• 17. the response entity contains an exceptionCode attribute value of "InvalidParameterValue".

And the actual test code, instead, uses this:

<ctl:with-param name="exceptionCodes">TileOutOfRange</ctl:with-param>

To Reproduce
Run the WMTS tests with a server following the specification ATS, and returns a PointIJOutOfRange code.
The test will fail, reporting though documentation that it's looking for InvalidParameterValue (but actually checking for TileOutOfRange.

Expected behavior
The test should pass

[aaime]

See #100 for a suggested fix
(cumulative for also the schema issue, but I can split it into two parts, if you prefer to merge separately)

[dstenger]

Thank you for reporting and creating a pull request. In general, we prefer two separate pull requests. However, in this case it is fine as the changes are quite compact.
We will review the provided PR soon.