feat(chart): Simplify to change log level in Kubernetes

[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

feat(chart): Simplify to change log level in Kubernetes

Motivation and Context

Sometimes, a few questions related to Selenium Grid deployed on vendors cloud K8s service with issues like Node could not register to Hub, and relevant logs given something like

10:25:20.758 INFO [NodeServer.execute] - Started Selenium node 4.14.1 (revision 03f8ede370): http://10.244.4.8:5555
10:25:20.777 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
10:25:30.781 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
10:25:40.782 INFO [NodeServer$1.lambda$start$1] - Sending registration event...

Then we get back to ask log level FINE to see lower debug logs for the problem troubleshooting.
With the Selenium Grid chart, the user needs more steps to do that, find all components and set extraEnvironmentVariables within SE_OPTS=--log-level FINE

Via this change, we try to simplify this config change by:

• Docker image side: adding a separate ENV SE_LOG_LEVEL to get input value, internally it would append value to SE_OPTS and start the components
• Chart side:
  • Adding a ConfigMap for logging options (https://www.selenium.dev/documentation/grid/configuration/cli_options/#logging). As of now only SE_LOG_LEVEL data is added
  • All other components container ENV refer to that ConfigMap for logging configs. (As the table matrix https://www.selenium.dev/documentation/grid/configuration/cli_options/#sections - Logging supports all components)
  • Chart value global.seleniumGrid.logLevel is used to set a specific value.

For example: If the user wants to change the log level to FINE, now it would be done by
helm upgrade -i test --set global.seleniumGrid.logLevel=FINE --values myConfigs.yaml selenium-grid-4.16.1-20231218.tgz

Added the test to ensure template renders config correctly

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!