Validate crs and valid domain during transactions

[dstenger]

Chapter A.2.18.2 of the WFS 2.0.0 states following:

...
(1.) Insert another feature with geometries where the value of the srsName parameter is not one of the SRS values the server claims to support in its capabilities document. Verify that the server responds with an exception.
(2.) Insert a final feature with geometries where the value of the srsName is one of the SRS values the server claims to support in its capabilities but the geometries in the insert action are encoded with an SRS that does not match the one asserted as the value of the srsName parameter. Verify that the server responds with an exception.

This enhancement enables those two behaviours for insert transactions:

1. A check is implemented if any srsName parameter value of the request is present in the capabilities document. If this is not the case, an exception is thrown.
2. A check is added if any used geometries are outside the valid domain of the corresponding SRS. If this is not the case, an exception is thrown.

[copierrj]

This pull request looks like it is still work in progress. Any update to report?

[tfr42]

It will checked against OGC TEAM engine with WFS 2.0 ETS against http://cite.deegree.org/deegree-webservices-3.4.0/