Add k6 binary provisioning preview

[pablochacin]

What?

Add an introduction to the Binary Provisioning feature to be released as experimental feature in v1.0.0

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)

[codebien]

The technical content looks good to me. I assume @heitortsergent will handle grammar and formatting.

[pablochacin]

@heitortsergent, the code execution is failing. I tried to skip but it is still being executed. Can you please help me with this? 🙏

[dgzlopes]

Content-wise, the PR LGTM. That said, given that the current state is the following:

The feature requires authentication to Grafana Cloud and therefore is supported only in the cloud run command.

Shouldn't this live in the Cloud docs? We could still have a reference in the extension sections... but yeah

[andrewslotin]

@dgzlopes,

Shouldn't this live in the Cloud docs?

I believe it should and it might make sense to document it from the perspective of being able to use k6 extensions in Grafana Cloud. The CLI support of Binary Provisioning is there to match the Cloud experience.

[andrewslotin]

Rephrased for readability.

[heitortsergent]

Made some small suggestions, but I'd like to change the structure a little bit so it follows our style guide. Do you mind if I make some changes directly to the branch @pablochacin?

We could also merge this after resolving the open comments, and I can made edits later if that's ok. 🤓

[heitortsergent]

Suggested change

	```windows-powershell
	```
	```windows
	```

Can we remove these since there are no specific commands for it?

[pablochacin]

@heitortsergent I think there should be, because this is available for Windows users, only that I don't have a windows machine to test them

[Lantero]

I'll approve it content/product wise, I will let Heitor add the grammar/structure sprinkles 🙂