Remove the deprecated k6/experimental/tracing

[mstoykov]

What?

Documentation changes around grafana/k6#3855

Checklist

• I have used a meaningful title for the PR.
• I have described the changes I've made in the "What?" section above.
• I have performed a self-review of my changes.
• I have run the npm start command locally and verified that the changes look good.

• I have made my changes in the docs/sources/next folder of the documentation.
• I have reflected my changes in the docs/sources/v{most_recent_release} folder of the documentation.
• I have reflected my changes in the relevant folders of the two previous k6 versions of the documentation (if still applicable to previous versions).

• I have made my changes in the docs/sources/next folder of the documentation.

Related PR(s)/Issue(s)

[inancgumus]

I don't know much about this project, but I wonder if we should remove the other references.

• k6-docs/src/data/markdown/docs/02 javascript api/07 k6-experimental.md

  Line 14 in dde5a2a

  | [tracing](/javascript-api/k6-experimental/tracing/) | Support for instrumenting HTTP requests with tracing information. |

• k6-docs/src/data/markdown/translated-guides/en/07 Testing Guides/02 Automated performance testing.md

  Line 260 in dde5a2a

  To bridge the gap, work out a way to correlate testing results with how you instrument your infrastructure and application code. For instance, connecting or building custom dashboards with test results or using [trace data from your tests](/javascript-api/k6-experimental/tracing/).

and so on.

[heitortsergent]

I think it makes sense to remove the other references as well @inancgumus. We can also include aliases in the jslib utils pages so if people try to access those pages they get redirected to the correct library instead of seeing a 404.

Let me know if you want me to take care of this @mstoykov and I can make the changes in this PR. 🙏

[mstoykov]

Good catch @inancgumus ... I think I just looked into next and not the other parts of the docs.

@heitortsergent I will be glad if you take care of this 🙇

[heitortsergent]

Actually, I looked into the other references and I think we can keep them. Since this is being removed in the next version of k6, it makes sense that we just remove them from the next folder. :)

I added aliases from the deleted pages to the http-instrumentation-tempo module, so if anyone had links with latest in it they should be redirected to the correct page and not see a 404.

[oleiade]

Merging this to move forward with the release process 🙇‍♂️