SECORE_Add support for URN not-completely-specified objects in REST URI

[Bang Pham Huu]

SECORE only support the official URN pattern

urn:ogc:def:objectType:authority:version:code
(e.g: localhost:8080/def/crs/EPSG/0/4326).

However, it needs to support an URN extension as in WMS 1.3, it has few CRS with parameters after the code in URL part,
e.g: localhost:8080/def/AUTO/1.3/42001/99/888

The formal definition for this URN extension (​https://portal.opengeospatial.org/files/?artifact_id=30575) is

URNs for not-completely-specified objects
A URN can also be used to denote a not-completely-specified object, which is specified
without the values of a few identified parameters. In this case, the URN value includes
the values for each identified parameter. 

To identify an object with two unspecified parameters, the URN shall have the form:
urn:ogc:def:objectType:authority:version:code:value1:value2 

SECORE already supports with ?key=value (but REST format /value1/value2/… is used in general), e.g:

localhost:8080/def/crs/AUTO/1.3/42001?lon=20

(lon is a variable in the CRS definition which will get value from the key-value of URL).

And requests like these are handled in ParameterizedCrsHandler class.