binary provisioning: GA updates

[pablochacin]

What?

Update description of binary provisioning with the enhancements introduced for GA

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/k6/next folder of the documentation.
• I have reflected my changes in the docs/sources/k6/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/k6/next folder of the documentation.

Related PR(s)/Issue(s)

Closes #1995

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[codebien]

Generally speaking I think we should remove the Binary Provisioning naming from the documentation as much as we can. It is an implementation detail for most of the users. What they care is the fact that they can run extensions directly with the official k6 binary.

[pablochacin]

Should we move this before custom builds?

[heitortsergent]

I think that's a good idea. 👍

[heitortsergent]

Left a few small comments. What do you think of changing the order of the headings, so it's:

• Before you begin
• Run a test with extensions
• Disable the Automatic Extension Resolution
• Enable community extensions
• Use unsupported extensions
• Limitations

So just moving the main action of running the test to be at the top.