Update base to use JDK21

[VietND96]

User description

Thanks for contributing to the Docker-Selenium project!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines, applied for this repository.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Supply for the change SeleniumHQ/selenium@2357514 gets effective for containers.
This change might help with SeleniumHQ/selenium#13718
It also might help #2169

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Enhancement

---

Description

• Updated the base Dockerfile to use JDK 21.

• Removed a specific dependency version for io.lettuce:lettuce-core.

---

Changes walkthrough 📝

	Relevant files
Enhancement	Dockerfile Update JDK version and clean dependencies                                Base/Dockerfile Updated JRE_VERSION from 17 to 21. Removed specific version for io.lettuce:lettuce-core. +1/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Dependency version control: Removing the explicit version pin of lettuce-core (previously 6.5.1.RELEASE) could potentially introduce security vulnerabilities if an older or vulnerable version gets pulled in. The comment on line 130 mentions this was specifically for CVE patches.

⚡ Recommended focus areas for review Dependency Removal Removal of specific lettuce-core version may reintroduce CVE vulnerabilities that were previously patched. Need to verify if the default version is secure. # Patch specific version for CVEs in the dependencies > /external_jars/.classpath_session_map.txt \

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Maintain explicit dependency version control Re-add the explicit version for lettuce-core dependency to prevent potential security vulnerabilities from transitive dependencies. Base/Dockerfile [129-131] org.seleniumhq.selenium:selenium-session-map-redis:${MVN_SELENIUM_VERSION} \ # Patch specific version for CVEs in the dependencies +io.lettuce:lettuce-core:6.5.1.RELEASE \ > /external_jars/.classpath_session_map.txt \ Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies that removing the explicit version of lettuce-core could expose the system to security vulnerabilities. Pinning dependency versions is crucial for security and stability.	9

[VietND96]

@joerg1985 JDK21 is updated and started deploying in Nightly images