feat: Java 25 docker images

[sfreudenthaler]

Context

I'd like to craft a story to take over the Java 25 builds from @wezell side of desk and get some idea with you on estimate. The first step story on the road should be pretty tight.

User Story

**AS A** dotcms user, 
**I WANT** a dotcms/dotcms docker image based on java 25 runtime for each release,
**SO THAT** I can start preparing for the sunset of dotÇMS based on Java 11 (announced in Q4 of 2025)  

REF

• Slack Message
• Blog post

[spbolton]

Refactored to move summary to separate epic from this user story. #34484 and a separate google doc for design and implementation discussion here https://docs.google.com/document/d/1Mg9eDKZ9TCuEyhv5M9YOn1XS_GMVGArhZpm5cIcvgUU/edit?tab=t.0#heading=h.8zdi1t7oecvu

[spbolton]

I would advise that we do not start with the release workflow, but focus on allowing version override on trunk, or nightly ( or a clone specific for this ) where the focus is creating a docker image and then we follow up with release as there are additional steps in the release workflow to consider. As release is now following the same patterns as the other core workflows, the work on trunk or nightly will then be directly available in the release workflow allowing follow up work to focus on the release specific steps.