Attempt to fix CSW GetRecords issue from mapstore

[pmauduit]

On current georchestra's geonetwork version (based of GN4.2), the following payload on the CSW endpoint (generated from the mapstore UI when trying to add a layer from the local catalogue) is translated to an invalid query sent to Elasticsearch:

<?xml version="1.0"?>
<csw:GetRecords xmlns:csw="http://www.opengis.net/cat/csw/2.0.2" xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmi="http://www.isotc211.org/2005/gmi" xmlns:ows="http://www.opengis.net/ows" service="CSW" version="2.0.2" resultType="results" startPosition="1" maxRecords="4">
  <csw:Query typeNames="csw:Record">
    <csw:ElementSetName>full</csw:ElementSetName>
    <csw:Constraint version="1.1.0">
      <ogc:Filter>
        <ogc:Or>
          <ogc:PropertyIsEqualTo>
            <ogc:PropertyName>dc:type</ogc:PropertyName>
            <ogc:Literal>dataset</ogc:Literal>
          </ogc:PropertyIsEqualTo>
          <ogc:PropertyIsEqualTo>
            <ogc:PropertyName>dc:type</ogc:PropertyName>
            <ogc:Literal>http://purl.org/dc/dcmitype/Dataset</ogc:Literal>
          </ogc:PropertyIsEqualTo>
        </ogc:Or>
      </ogc:Filter>
    </csw:Constraint>
  </csw:Query>
</csw:GetRecords>

It turns out it works if the purl.org url is double-quoted. @cmangeat already provided a fix into an "unofficial" branch from this repository. This PR is just about cherry-picking the work and attempt to fix the IT testsuite.

[pmauduit]

I had a talk with @cmangeat who told me that his "heroïc fix" is heroïc in the sense we should definitely not do it this way.

[pmauduit]

But at least, my spec is passing with the following PR:

[fvanderbiest]

I had a talk with @cmangeat who told me that his "heroïc fix" is heroïc in the sense we should definitely not do it this way.

I see it has been fixed upstream on 4.2.6, which we are upgrading to on geOrchestra master.
Hence this looks like an acceptable local fix for 23.0.

The current PR on the branch targeted by geOrchestra master can be discarded IMO.