Tune start script for OpenJDK 25 and use it in Docker image

[fab-10]

PR description

GC configuration tuning for Java25 to make it release the heap memory not used to the OS, and have pattern closer to Java21 (actually with this setup Java25 on average has less wasted heap) and base the Docker image on Java25

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• spotless: ./gradlew spotlessApply
• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests
• hive tests: Engine or other RPCs modified?

[usmansaleem]

LGTM.
Also, we can probably use jlink command as a docker build step to prepare the JVM similar to how Temurin overview mentions (Consensys Web3Signer and Teku also uses similar approach) https://hub.docker.com/_/eclipse-temurin. This would ease up architect/checksum requirements.

[fab-10]

LGTM. Also, we can probably use jlink command as a docker build step to prepare the JVM similar to how Temurin overview mentions (Consensys Web3Signer and Teku also uses similar approach) https://hub.docker.com/_/eclipse-temurin. This would ease up architect/checksum requirements.

IDK about jlink could you propose a patch for that approach since you have already used it?