analyze built-in extensions

[pablochacin]

What?

Analyze if the built-in extensions satisfy the dependencies before provisioning a new custom binary

Why?

Binary provisioning is available in any k6 binary, including those with built-in extensions. Considering these extensions can save unnecessary custom binary provisionings.

Checklist

• [x] I have performed a self-review of my code.
• [x] I have commented on my code, particularly in hard-to-understand areas.
• [x] I have added tests for my changes.
• [x] I have run linter and tests locally (make check) and all pass.

Checklist: Documentation (only for k6 maintainers and if relevant)

Please do not merge this PR until the following items are filled out.

• [ ] I have added the correct milestone and labels to the PR.
• [ ] I have updated the release notes: link
• [ ] I have updated or added an issue to the k6-documentation: grafana/k6-docs#NUMBER if applicable
• [ ] I have updated or added an issue to the TypeScript definitions: grafana/k6-DefinitelyTyped#NUMBER if applicable

Related PR(s)/Issue(s)

Depens on https://github.com/grafana/k6/pull/4801

Closes https://github.com/grafana/k6/issues/4697