feature info manager: preserve order of feature info format

Changes to the feature info manager caused deegree to fail some tests in the CITE WMS 1.1.1 TestSuite. The cause was tracked down to a change in order of the list of supported get feature info formats in the capabilities document.

The test suite expects that the Content-Type response header corresponds to the requested info format. This requested info format used by the tests is however not fixed, but a format is chosen by inspecting the content of the capabilities document. Changes to the feature info manager changed the order of info format in that document and therefore changed the format used in the test requests.

Another factor in the test failure was that Tomcat always appends the encoding to the Content-Type, resulting in: ${format};charset=${encoding}. The CITE tests are fine with that unless the resulting string contains more than one semicolon. In that case it concludes that the requested format and the returned format do not match. This happened when a format was chosen that already contains a semicolon, like: application/gml+xml; version=3.2.

The commit in this pull requests restores the list of supported feature info formats into what is previously was.