[GEOS-11702] GeoFence: major libs update

[etj]

Update many libs according to GeoFence 3.8

Major points:

• update of hibernate / hibernate spatial
• use of an H2 version not compatible with other plugins and previous geofence version. This part has been documented in the revised doc pages (installation/migrations).

GeoFence 3.8 SNAPSHOT is not merged into geofence/main yet, but has been already built and deployed in the osgeo maven repo.

Checklist

• I have read the contribution guidelines.
• I have sent a Contribution Licence Agreement (not required for small changes, e.g., fixing typos in documentation).
• First PR targets the main branch (backports managed later; ignore for branch specific issues).
• All the build checks are green (see automated QA checks).

For core and extension modules:

• New unit tests have been added covering the changes.
• Documentation has been updated (if change is visible to end users).
• The REST API docs have been updated (when changing configuration objects or the REST controllers).
• There is an issue in the GeoServer Jira (except for changes that do not affect administrators or end users in any way).
• Commit message(s) must be in the form [GEOS-XYZWV] Title of the Jira ticket.
• Bug fixes and small new features are presented as a single commit.
• Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

[etj]

There's a single error when compiling with JDK21:

Java 21 (65) is not supported by the current version of Byte Buddy which officially supports Java 20 (64) - update Byte Buddy or set net.bytebuddy.experimental as a VM property

Byte Buddy is used by hibernate instead of javaassist since version 5.3CR2 (where long ago javassist replaced cglib)

[aaime]

I would indicate that it's also safe to remove (it is, right?), in other words, that it's possible to use GeoFence with NetCDF/Grib provided the H2 v2 database is removed and the rule storage is moved to an external database.

I see it's written down in the same page, but some careless user might not read to the end, better to inform them now and indicate there are instructions later in the page.

[aaime]

Is it needed? The dependency towards gs-geofence-server should be enough, it's already declared as a dependency there.

[etj]

Without it, mvn will usee the 1.1 version :|

[aaime]

Wondering if we shoud have a profile to enable/disable this dependency.
Use case, starting GeoServer during development with both geofence and netcdf, with this setup it would be impossible...

[aaime]

Looks like we have a legit failure under Java 21:

2025-02-04T15:09:34.6500839Z WARNING: Dynamic loading of agents will be disallowed by default in a future release
2025-02-04T15:09:35.1389246Z 15:09:35,138 [ERROR] Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.992 s <<< FAILURE! - in org.geoserver.geofence.server.internal.SecurityContextUserResolverTest
2025-02-04T15:09:35.1394297Z 15:09:35,139 [ERROR] getRoles(org.geoserver.geofence.server.internal.SecurityContextUserResolverTest)  Time elapsed: 0.838 s  <<< ERROR!
2025-02-04T15:09:35.1395473Z org.mockito.exceptions.base.MockitoException: 
2025-02-04T15:09:35.1396042Z 

while not yet officially supported, we're keeping the entire GeoServer working under Java 21 too.

Saw your comment about it only now. At a minimum, disable the test under Java 21, the builds must be all green.