[Request] Provide image for JDK 25+36 as 25.0.0_36

For some reason, Oracle labels the initial release of a major JDK version, as e.g. `25`, followed by `25.0.1`, `25.0.2`...
This is what happened for [JDK 24](https://www.oracle.com/java/technologies/javase/24all-relnotes.html), [JDK 23](https://www.oracle.com/java/technologies/javase/23all-relnotes.html), [JDK 22](https://www.oracle.com/java/technologies/javase/22all-relnotes.html), etc.
I googled a bit but could find a reason why the initial release is not e.g. `25.0.0`.

This may seem a trivial issue, but it's actually causing some issues with tools (like Renovate Bot) which look for a specific pattern in versions.
For example, I currently reference version `eclipse-temurin:21.0.8_9-jdk@sha256:03e5fbb9980a03e4b3d11676082650a4443108aaf1f7b7d9cc338171c5a90070` in my Dockerfile, GitLab CI files, etc.
At the moment, I can only replace it with `eclipse-temurin:25_36-jdk@sha256:...`, which is confusing as it appears as if that the change introduced a lost of "version precision".

I see that some vendors _did_ release a Docker image for JDK 25 as `25.0.0`:
- [azul/zulu-openjdk](https://hub.docker.com/r/azul/zulu-openjdk/tags?name=25.0.0)
- [amazoncorretto](https://hub.docker.com/_/amazoncorretto/tags?name=25.0.0)

Some did not:
- [bellsoft/liberica-openjdk-debian](https://hub.docker.com/r/bellsoft/liberica-openjdk-debian/tags?name=25.0.0)
- [sapmachine](https://hub.docker.com/_/sapmachine/tags?name=25.0.0)
- and thus [eclipse-temurin](https://hub.docker.com/_/eclipse-temurin/tags?name=25.0.0)

Could you consider doing like Azul and Amazon, and provide JDK 25+36 as a Docker image with tag `25.0.0_36`?

Start by tracing the repository's Dockerfiles and scripts that generate or publish image tags. Check how the JDK 25 build is represented, then verify that the JDK 25+36 image is also published as 25.0.0_36 without changing existing tags.

Written by the indexing model from the issue text.