[FLINK-33291][build] Sets the enforced range for Maven and JDK within the release profile

[XComp]

What is the purpose of the change

We want to enforce the Maven and JDK version for releases based on the versions that are used in Flink's CI pipeline to ensure a certain level of quality control.

Brief change log

• Adds proper range for Maven and JDK
• For the JDK version, it looks like we cannot use ${target.java.version} or [1.8] to cover any minor releases

Verifying this change

Manual verification by running ./mvn -pl flink-annotations -DskipTests -Prelease validate with different Java and Maven versions

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• 482349a Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[snuyanzin]

I checked locally that it works

[XComp]

Thanks for the approval. I did a slight adjustment to the comment after confirming with Chesnay. I will go ahead and create backports.