GWC make use of XMLUtils to make better use of GeoTools Hints

[jodygarnett]

Makes use of the new XMLUtils utility methods introduced following PR:

• [GEOT-7898] Setup XMLUtils to assist in use of DefaultEntityResolver geotools/geotools#5639
  Contains API Change to XMLUtils
• [GEOS-12110] Make use of XMLUtils for better integration with GeoTools Hints geoserver/geoserver#9502

This will need to be merged at the same time. I have named the branches the same, perhaps we can adjust the "downstream integration workflow" to look for same branch to check out.

Before merging this PR please re-run integration test upstream on geotools/geotools#5639 (it looks for branches with the same name default-entity-resolver-check.)

This PR supersedes #1533

[jodygarnett]

Closing / reopen to test against new GeoTools SNAPSHOTs

[jodygarnett]

@groldan it looks like you wrote the test which is failing:

java.lang.AssertionError: Concurrent migrateForeignKeys threw on 1/4 threads; see suppressed
        at org.geowebcache.diskquota.jdbc.AbstractForeignKeyMigrationTest.migrateIsConcurrentStartupSafe(AbstractForeignKeyMigrationTest.java:136)
...
Suppressed: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [ALTER TABLE tilepage DROP CONSTRAINT tilepage_tileset_id_fkey]
        at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:134)
...
        Caused by: org.postgresql.util.PSQLException: ERROR: constraint "tilepage_tileset_id_fkey" of relation "tilepage" does not exist
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2904)
...

Do you have any insight into why this may be failing? Presently failing on JDK21.

• Update 1: I cannot reproduce the failure locally using JDK17
• Update 2: Or JDK21
• Oh wait now the error is gone, I guess this test I just not stable...