feat: Update NodeChrome support latest version from GoogleChromeLabs

[VietND96]

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

Motivation and Context

1. GoogleChromeLabs support a dashboard for versions https://googlechromelabs.github.io/chrome-for-testing
   NodeChrome image can get Chrome version based on ARG CHROME_VERSION with below inputs

       LATEST_RELEASE_STABLE
       LATEST_RELEASE_BETA
       LATEST_RELEASE_DEV
       LATEST_RELEASE_CANARY
       121 (e.g specific major version)
       119.0.6045.105 (e.g specific full version)

By default, ARG CHROME_DRIVER_VERSION follows CHROME_VERSION. Chrome Driver version can be specified independently with the same support inputs above.

2. Add feat [🚀 Feature]: Specify driver location to avoid Selenium Manager #2008
   [Reverted as duplicate with Setting driver and browser path via configuration #2017]

3. After setting java prop -Dwebdriver.chrome.driver for NodeChrome. The below issue could be seen always.
   Note: If removing this prop in the command start node, the issue is over, still not figure out reason for this strange

selenium.common.exceptions.SessionNotCreatedException: Message: Could not start a new session. Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 500. Message: session not created: Chrome failed to start: exited normally.
  (session not created: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /opt/google/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.) 

Updated
The above issue can be fixed by adding to node stereotype with the binary location, get from #2017
{"browserName": "chrome", "browserVersion": "119.0", "platformName": "Linux", "goog:chromeOptions": {"binary": "/usr/bin/google-chrome"}}
Change in test has been reverted.

4. Add test for helm chart, which covers feat(chart): Add chart parameter ingress.paths to configure custom paths #1994

5. Fix Firefox WebDriver issue when run with random user (true) [🐛 Bug]: Could not start a new session. Response code 500. Message: Failed to read marionette port #2020. Add back test case in workflow

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.

[diemol]

Thank you, @VietND96!

Feature 2 is not needed as we want to set the browser driver always.

Point 3 has been fixed by setting the browser path in the stereotype.

[VietND96]

Thanks for your review @diemol !
I have reverted feat 2, keeping it the same as #2017 only.

[diemol]

Thank you, @VietND96!