Fix link to extensions community forum

Author: oleiade

src/data/markdown/docs/07 extensions/01 Get started/04 Create/01 JavaScript Extensions.md

@@ -33,7 +33,7 @@ $ go install go.k6.io/xk6/cmd/xk6@latest
   ```
 
 1. In the directory, make a Go file for your JavaScript extension.
-  
+
   A simple JavaScript extension requires a struct that exposes methods called by the test script.
 
   <!-- TODO: A better trivial example? A coin flip perhaps? -->
@@ -340,7 +340,7 @@ INFO[0000] Active VUs: 2, Iteration: 2, VU ID: 2, VU ID from runtime: 2  source=
 - Use the registry's [`NewMetric`](https://pkg.go.dev/go.k6.io/k6/metrics#Registry.NewMetric) method to create
   custom metrics; to emit them, use [`metrics.PushIfNotDone()`](https://pkg.go.dev/go.k6.io/k6/metrics#PushIfNotDone).
 
-> Questions? Feel free to join the discussion on extensions in the [k6 Community Forum](https://community.grafana.com/c/extensions/).
+> Questions? Feel free to join the discussion on extensions in the [k6 Community Forum](https://community.grafana.com/c/grafana-k6/extensions/82).
 
 Next, create an [Output extension](/extensions/get-started/create/output-extensions/) to publish test metrics
 to a destination not already supported by k6.

src/data/markdown/docs/07 extensions/01 Get started/04 Create/02 Output Extensions.md

@@ -242,5 +242,5 @@ Your output should look something like this:
 - Use the [project template](https://github.com/grafana/xk6-output-template) as a starting point
   for your output extension.
 
-> Questions? Feel free to join the discussion on extensions in the [k6 Community Forum](https://community.grafana.com/c/extensions/).
+> Questions? Feel free to join the discussion on extensions in the [k6 Community Forum](https://community.grafana.com/c/grafana-k6/extensions/82).
 

src/data/markdown/docs/07 extensions/03 Guides/build-k6-using-docker.md

@@ -41,7 +41,7 @@ docker run --rm -e GOOS=windows -v "%cd%:/xk6" ^
 
 </CodeGroup>
 
-This creates a `k6` (or `k6.exe`) binary in the current working directory. 
+This creates a `k6` (or `k6.exe`) binary in the current working directory.
 
 To build the binary with concrete versions, see the example below (k6 `v0.45.1`, xk6-kafka `v0.19.1`, and xk6-output-influxdb `v0.4.1`):
 
@@ -84,7 +84,7 @@ The example command line may look a bit intimidating at first, but let's focus o
 docker run --rm -u "$(id -u):$(id -g)" -v "${PWD}:/xk6"
 ```
 
-This tells Docker to run a new container from an image. 
+This tells Docker to run a new container from an image.
 - `--rm` means the container will be destroyed once your build is completed.
 - `-u` specifies the user and group IDs of the account on the host machine. This is important for the `k6` file to have the same file permissions as the host user.
 - `-v` is required to mount the current working directory inside the container, so that the `k6` binary can be written to it.
@@ -168,5 +168,5 @@ k6.exe run my-script.js
 
 ## Encountering issues?
 
-If you're having issues, search the [k6 Community Forum](https://community.grafana.com/c/extensions/). 
+If you're having issues, search the [k6 Community Forum](https://community.grafana.com/c/grafana-k6/extensions/82).
 Someone may have had the same issue in the past.