GeoTools 32.0 update and JTS 1.20.0 update

[jodygarnett]

This PR resolves #8183 (in response to CVE-2024-36404 ).

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

This change is to support GeoCat Find catalogue.

[jahow]

Thanks! I tried out several map-related features on this branch and had no issue.

[josegar74]

I've done some testing and it seems working fine, but the commit message seems not accurate: GeoTools 30.0 update

It's an update to version 32.0.

@jodygarnett can you update it?

[geonetworkbuild]

The backport to 4.2.x failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply f9abda23dc... GeoTools 32.0 update and JTS 1.20.0 update
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout

Auto-merging pom.xml
CONFLICT (content): Merge conflict in pom.xml

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-8485-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick f9abda23dc56ed3ef74af230a9ea031ac9ca3abe
# Push it to GitHub
git push --set-upstream origin backport-8485-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x

Then, create a pull request where the base branch is 4.2.x and the compare/head branch is backport-8485-to-4.2.x.

[jodygarnett]

See related #8490

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud