Fixed exception code and status code of response when non existent lock is requested

[dstenger]

This fix targets the locking functionality of WFS 2.0.0.

Previously, when LockFeature was requested with a non existent lockId, the WFS 2.0.0 threw an InvalidParameterValue exception with status code 400.

The specification says that following is expected:

• status code: 403
• exception code: LockHasExpired

Excerpt from WFS 2.0.0 specification:

12.2.4.2 lockId parameter

A lockId parameter specified within a LockFeature operations shall be used to reset the expiry time of an existing lock.
...
Such a LockFeature operation shall be executed before the specified lock has expired; otherwise the server shall raise a LockHasExpired exception (see Table 3).
...

This fix corrects the status and exception codes to implement the expected behaviour.

In addition, deegree now passes following tests of the CITE WFS 2.0 test suite (Locking CC) [1]:

• "Reset Nonexistent Lock"
• "Lock All Query Results_20 Seconds"

[1] http://cite.opengeospatial.org/teamengine/