chore: [release-2.9.x] docs: Replace instances of k6.io/docs with grafana.com/docs/k6 (#13310)

Co-authored-by: Heitor Tashiro Sergent <heitortsergent@gmail.com>

docs/sources/send-data/k6/_index.md

@@ -9,8 +9,8 @@ weight:  900
 
 # Using k6 for load testing
 
-Grafana [k6](https://k6.io) is a modern load-testing tool.
-Its clean and approachable scripting [API](https://k6.io/docs/javascript-api/)
+Grafana [k6](https://grafana.com/oss/k6/) is a modern load-testing tool.
+Its clean and approachable scripting [API](https://grafana.com/docs/k6/latest/javascript-api/)
 works locally or in the cloud.
 Its configuration makes it flexible.
 
@@ -55,7 +55,7 @@ Use the custom-built k6 binary in the same way as a non-custom k6 binary:
 ```
 
 `test.js` is a Javascript load test.
-Refer to the [k6 documentation](https://k6.io/docs/) to get started.
+Refer to the [k6 documentation](https://grafana.com/docs/k6/latest/) to get started.
 
 ### Scripting API
 
@@ -75,7 +75,7 @@ Classes of this module are:
 | `Client` | client for writing and reading logs from Loki |
 
 `Config` and `Client` must be called on the k6 init context (see
-[Test life cycle](https://k6.io/docs/using-k6/test-life-cycle/)) outside of the
+[Test life cycle](https://grafana.com/docs/k6/latest/using-k6/test-lifecycle/)) outside of the
 default function so the client is only configured once and shared between all
 VU iterations.
 

docs/sources/send-data/k6/query-scenario.md

@@ -96,7 +96,7 @@ export default () => {
 ## Metrics
 
 The extension collects metrics that are printed in the
-[end-of-test summary](https://k6.io/docs/results-visualization/end-of-test-summary/) in addition to the built-in metrics.
+[end-of-test summary](https://grafana.com/docs/k6/latest/results-output/end-of-test/) in addition to the built-in metrics.
 These metrics are collected only for instant and range queries.
 
 | name                              | description                                  |

docs/sources/send-data/k6/write-scenario.md

@@ -59,17 +59,17 @@ These parameters can be adjusted in the load test:
 
 * The way to run k6
 
-    k6 supports three [execution modes](https://k6.io/docs/get-started/running-k6/#execution-modes) to run a test: local, distributed, and cloud.
+    k6 supports three [execution modes](https://grafana.com/docs/k6/latest/get-started/running-k6/#execution-modes) to run a test: local, distributed, and cloud.
     Whereas running your k6 load test from a single (local
     or remote) machine is easy to set up and fine for smaller Loki clusters,
     the single machine does not load test large Loki installations,
     because it cannot create the data to saturate the write path.
-    For larger tests, consider [these optimizations](https://k6.io/docs/testing-guides/running-large-tests/), or run them in [Grafana Cloud k6](/products/cloud/k6) or a Kubernetes cluster with the [k6 Operator](https://github.com/grafana/k6-operator).
+    For larger tests, consider [these optimizations](https://grafana.com/docs/k6/latest/testing-guides/running-large-tests/), or run them in [Grafana Cloud k6](/products/cloud/k6) or a Kubernetes cluster with the [k6 Operator](https://github.com/grafana/k6-operator).
 
 ## Metrics
 
 The extension collects two metrics that are printed in the
-[end-of-test summary](https://k6.io/docs/results-visualization/end-of-test-summary/) in addition to the built-in metrics.
+[end-of-test summary](https://grafana.com/docs/k6/latest/results-output/end-of-test/) in addition to the built-in metrics.
 
 | name | description |
 | ---- | ----------- |
@@ -80,7 +80,7 @@ The extension collects two metrics that are printed in the
 
 An HTTP request that successfully pushes logs to Loki
 responds with status `204 No Content`.
-The status code should be checked explicitly with a [k6 check](https://k6.io/docs/javascript-api/k6/check-val-sets-tags/).
+The status code should be checked explicitly with a [k6 check](https://grafana.com/docs/k6/latest/javascript-api/k6/check/).
 
 
 ## Javascript example