Allow external uri to be configurable for components that support server functionality - #12491 (#1448)

Allow external uri to be configurable for components that support server functionality.

SE nodes might be behind some sort of proxy exposed to hub on a
different hostname(/ip) and/or port than component would by default
report themselves (e.g.: hub and nodes are in different k8s clusters
 and services are exposed via node ports).

Fixes #12491

Co-authored-by: Diego Molina <[email protected]>

[deploy site]

Author: utamas

website_and_docs/content/documentation/grid/configuration/cli_options.en.md

@@ -250,6 +250,7 @@ pull request updating this page.
 
 | Option | Type | Value/Example | Description |
 |---|---|---|---|
+| `--external-url`      | string  | `http://10.0.1.1:33333` | External URL where component is generally available. Useful on complex network topologies when components are on different networks and proxy servers are involved.                                                                                                                   |
 | `--allow-cors` | boolean | `true` | Whether the Selenium server should allow web browser connections from any host |
 | `--host` | string | `localhost` | Server IP or hostname: usually determined automatically. |
 | `--bind-host` | boolean | `true` | Whether the server should bind to the host address/name, or only use it to" report its reachable url. Helpful in complex network topologies where the server cannot report itself with the current IP/hostname but rather an external IP or hostname (e.g. inside a Docker container) |