Browser: Use external API

[AgnesToulet]

This adds a call to an external API in /browser.php.

This allows to test features that we are currently implementing in k6/browser like page.route function and adds some CORS to test for more complex use cases.

[DefCon-007]

@AgnesToulet Is it possible to add it in one of the quickpizza pages or maybe add a new route for it in place of updating test.k6.io?
The thing is, test.k6.io was the old website, and it was migrated here primarily for backward compatibility when we merged all the test services into a single one.

[ankur22]

@AgnesToulet Is it possible to add it in one of the quickpizza pages or maybe add a new route for it in place of updating test.k6.io?
The thing is, test.k6.io was the old website, and it was migrated here primarily for backward compatibility when we merged all the test services into a single one.

@DefCon-007 I think that makes sense, but i'm wondering if we can let this one through?

Eventually, I think we will want to make modifications to either quickpizza or add a test page specifically to test all the edge cases and different features of the k6 browser module.

We also want/need to build a website that is more representative of what our users/customers have built (high number of background async requests, large media files, iframes, CORS related issues, shadow DOM, all the HTML elements under the sun 😅 etc). That's a whole other thing though.

[DefCon-007]

@ankur22 I apologise for the delayed response. I would still recommend adding the functionality to the Quickpizza web app rather than the legacy page. The legacy pages were added for backward compatibility with existing examples as we lacked the resources to update all of them. Modifying these pages implies that we are updating and continuing to use the old examples. Therefore, I would request that the functionality be added to one of the Quickpizza pages.