openjdk21, openjfx21: update

[wegank]

Description of changes

Split from #286267.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[thiagokokada]

Any reason for this to be marked as draft?

[wegank]

Any reason for this to be marked as draft?

I'm not sure if it can target master, although this PR's rebuilds are much faster than 17's on my machine.

[raboof]

Perhaps this should indeed target staging...

I've tested building and running ammonite (which is a binary), and building and running s3proxy (which is built with maven), both seemed fine.

Testing everything doesn't seem appropriate, but perhaps we should come up with a 'standard' set of tests we want to run when updating the default jdk?

[github-actions]

Successfully created backport PR for staging-24.05:

• [Backport staging-24.05] openjdk21, openjfx21: update #316508