moving to jdk25 and javafx25

[shroffk]

Checklist

• Testing:

  • The feature has automated tests
  • Tests were run
  • If not, explain how you tested your changes

• Documentation:

  • The feature is documented
  • The documentation is up to date
  • Release notes:
    • Added an entry if the change is breaking or significant
    • Added an entry when adding a new feature

[sonarqubecloud]

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 SonarQube Cloud

[shroffk]

So I decided to break the work into 3 PRs, each on its own branch...the hope is that this would help us address issues arising from the appropriate associated change ( is the issue because of JDK upgrade or spring upgrade ) on the correct branch and also create milestones

#3906 first to be merged, just move jdk and javafx
#3907 move to spring 4 - new security module, new elastic client
#3899 this is the final merge into the master with all the above changes vetted

[kasemir]

I don't understand what's going on with spring but the basic move to JDK25 should be fine, I've beed using JDK25 during development and didn't experience problems