Backport JS extension changes to v1.0.x and v1.1.x

Author: andrewslotin

docs/sources/k6/v1.0.x/extensions/create/javascript-extensions.md

@@ -161,6 +161,14 @@ INFO[0000] false, 1 is NOT greater than 3                source=console
 
 ## Use the advanced module API
 
+{{< admonition type="caution" >}}
+
+The advanced module API adds significant complexity to your extension. Consider whether you actually need access to internal
+k6 objects before implementing this pattern. For simple modules that don't need VU state or runtime access, the basic approach
+shown above is sufficient.
+
+{{< /admonition >}}
+
 Suppose your extension needs access to internal k6 objects to, for example, inspect the state of the test during execution.
 We will need to make slightly more complicated changes to the above example.
 
@@ -174,12 +182,6 @@ to access the [`modules.VU`](https://pkg.go.dev/go.k6.io/k6/js/modules#VU) to in
 Additionally, there should be a root module implementation of the [`modules.Module`](https://pkg.go.dev/go.k6.io/k6/js/modules#Module)
 interface to serve as a factory of `Compare` instances for each VU.
 
-{{< admonition type="caution" >}}
-
-The significance depends on the size of your module.
-
-{{< /admonition >}}
-
 Here's what that would look like:
 
 {{< code >}}
@@ -323,9 +325,6 @@ INFO[0000] Active VUs: 2, Iteration: 1, VU ID: 1, VU ID from runtime: 1  source=
 INFO[0000] Active VUs: 2, Iteration: 2, VU ID: 2, VU ID from runtime: 2  source=console
 ```
 
-> For a more extensive usage example of this API, look at the
-> [`k6/execution`](https://github.com/grafana/k6/blob/master/js/modules/k6/execution/execution.go) module.
-
 ## Things to keep in mind
 
 - The code in the `default` function (or another function specified by

docs/sources/k6/v1.1.x/extensions/create/javascript-extensions.md

@@ -161,6 +161,14 @@ INFO[0000] false, 1 is NOT greater than 3                source=console
 
 ## Use the advanced module API
 
+{{< admonition type="caution" >}}
+
+The advanced module API adds significant complexity to your extension. Consider whether you actually need access to internal
+k6 objects before implementing this pattern. For simple modules that don't need VU state or runtime access, the basic approach
+shown above is sufficient.
+
+{{< /admonition >}}
+
 Suppose your extension needs access to internal k6 objects to, for example, inspect the state of the test during execution.
 We will need to make slightly more complicated changes to the above example.
 
@@ -174,12 +182,6 @@ to access the [`modules.VU`](https://pkg.go.dev/go.k6.io/k6/js/modules#VU) to in
 Additionally, there should be a root module implementation of the [`modules.Module`](https://pkg.go.dev/go.k6.io/k6/js/modules#Module)
 interface to serve as a factory of `Compare` instances for each VU.
 
-{{< admonition type="caution" >}}
-
-The significance depends on the size of your module.
-
-{{< /admonition >}}
-
 Here's what that would look like:
 
 {{< code >}}
@@ -323,9 +325,6 @@ INFO[0000] Active VUs: 2, Iteration: 1, VU ID: 1, VU ID from runtime: 1  source=
 INFO[0000] Active VUs: 2, Iteration: 2, VU ID: 2, VU ID from runtime: 2  source=console
 ```
 
-> For a more extensive usage example of this API, look at the
-> [`k6/execution`](https://github.com/grafana/k6/blob/master/js/modules/k6/execution/execution.go) module.
-
 ## Things to keep in mind
 
 - The code in the `default` function (or another function specified by