[ci] Update tag 4.28.0-20250120 in docs and files

[skip test]

Author: selenium-ci

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -56,7 +56,7 @@ body:
     attributes:
       label: Docker Selenium version (image tag)
       description: What version of Docker Selenium are you using?
-      placeholder: 4.27.0-20250101? Please use the full tag, avoid "latest"
+      placeholder: 4.28.0-20250120? Please use the full tag, avoid "latest"
     validations:
       required: true
   - type: input

.keda/README.md

@@ -13,9 +13,9 @@ The stable implementation will be merged to the upstream KEDA repository frequen
 Replace the image registry and tag of these KEDA components with the patched image tag:
 
 ```bash
-docker pull selenium/keda:2.16.1-selenium-grid-20250101
-docker pull selenium/keda-metrics-apiserver:2.16.1-selenium-grid-20250101
-docker pull selenium/keda-admission-webhooks:2.16.1-selenium-grid-20250101
+docker pull selenium/keda:2.16.1-selenium-grid-20250120
+docker pull selenium/keda-metrics-apiserver:2.16.1-selenium-grid-20250120
+docker pull selenium/keda-admission-webhooks:2.16.1-selenium-grid-20250120
 ```
 
 Besides that, you also can use image tag `latest` or `nightly`.
@@ -27,15 +27,15 @@ If you are deploying KEDA core using their official Helm [chart](https://github.
     keda:
       registry: selenium
       repository: keda
-      tag: "2.16.1-selenium-grid-20250101"
+      tag: "2.16.1-selenium-grid-20250120"
     metricsApiServer:
       registry: selenium
       repository: keda-metrics-apiserver
-      tag: "2.16.1-selenium-grid-20250101"
+      tag: "2.16.1-selenium-grid-20250120"
     webhooks:
       registry: selenium
       repository: keda-admission-webhooks
-      tag: "2.16.1-selenium-grid-20250101"
+      tag: "2.16.1-selenium-grid-20250120"
 ```
 
 If you are deployment Selenium Grid chart with `autoscaling.enabled` is `true` (implies installing KEDA sub-chart), KEDA images registry and tag already set in the `values.yaml`. Refer to list [configuration](../charts/selenium-grid/CONFIGURATION.md).

NodeDocker/config.toml

@@ -2,9 +2,9 @@
 # Configs have a mapping between the Docker image to use and the capabilities that need to be matched to
 # start a container with the given image.
 configs = [
-    "selenium/standalone-firefox:4.27.0-20250101", '{"browserName": "firefox", "platformName": "linux"}',
-    "selenium/standalone-chrome:4.27.0-20250101", '{"browserName": "chrome", "platformName": "linux"}',
-    "selenium/standalone-edge:4.27.0-20250101", '{"browserName": "MicrosoftEdge", "platformName": "linux"}'
+    "selenium/standalone-firefox:4.28.0-20250120", '{"browserName": "firefox", "platformName": "linux"}',
+    "selenium/standalone-chrome:4.28.0-20250120", '{"browserName": "chrome", "platformName": "linux"}',
+    "selenium/standalone-edge:4.28.0-20250120", '{"browserName": "MicrosoftEdge", "platformName": "linux"}'
     ]
 
 # URL for connecting to the docker daemon
@@ -14,7 +14,7 @@ configs = [
 # socat -4 TCP-LISTEN:2375,fork UNIX-CONNECT:/var/run/docker.sock
 url = "http://127.0.0.1:2375"
 # Docker image used for video recording
-video-image = "selenium/video:ffmpeg-7.1-20250101"
+video-image = "selenium/video:ffmpeg-7.1-20250120"
 
 # Uncomment the following section if you are running the node on a separate VM
 # Fill out the placeholders with appropriate values