Feat: support grid basic auth on helm chart

[trungprivate]

Description

Simple change to allow Selenium Grid basic auth to be enabled/disabled through the values.yaml file when deploying via the Helm chart.

Motivation and Context

Currently, it is not straightforward to enable basic auth because:

1. Selenium grid URLs used for internal communication between components are calculated using helpers (_helpers.tpl) that do not take basic auth into consideration.
2. Autoscaling HPA URL is determined using (1) - therefore autoscaling will not work when basic auth is enabled unless HPA URL is explicitly set without using helpers. This causes duplication of configuration.
3. Basic auth settings need to be applied to either the hub or router, depending on isolated components set up

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.

Summary of changes:

1. Updated values.yaml template file to add new configuration items for basic auth
2. Updated helpers to correctly set seleniumGrid.url and seleniumGrid.graphqlURL when basic auth is enabled
3. Updated hub and router deployment templates to incorporate basic auth environment variables if basic auth is enabled

[CLAassistant]

All committers have signed the CLA.

[diemol]

I don't follow. Basic Auth in Grid is meant for the public endpoints, why do you say it is needed for internal components?

[trungprivate]

Hi @diemol - It is because the HPA URL needs to have the basic auth details in the URL. Please refer to this issue for more details: #1890

[diemol]

Thank you