Upgrade Maven dependencies to latest stable releases

[Copilot]

Analyzed project dependencies and upgraded 14 to their latest stable versions using Maven Versions Plugin.

Maven Plugins (4)

• flatten-maven-plugin: 1.7.2 → 1.7.3
• maven-surefire-plugin: 3.5.3 → 3.5.4
• maven-failsafe-plugin: 3.5.3 → 3.5.4
• maven-javadoc-plugin: 3.11.3 → 3.12.0

Libraries (10)

• avro: 1.12.0 → 1.12.1
• gson: 2.13.1 → 2.13.2
• groovy: 3.0.22 → 3.0.25
• groovy-jsr223: 4.0.28 → 4.0.29
• jakarta.xml.bind-api: 4.0.2 → 4.0.4
• mysql-connector-j: 9.4.0 → 9.5.0
• nashorn-core: 15.6 → 15.7
• prometheus-metrics-exporter-pushgateway: 1.4.1 → 1.4.2
• quartz: 2.5.0 → 2.5.1
• xmlunit: 2.10.4 → 2.11.0

Exclusions

Excluded beta/milestone/RC versions, major version upgrades (lettuce 6→7, jruby 9→10, log4j 2→3), and Derby 10.17.1.0 (known build failures per existing FIXME).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• jfrog-prod-use1-shared-virginia-main.s3.amazonaws.com
• repo.spring.io (HTTP Only)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

check if there are maven dependencies that can be upgraded to a newer release version

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.