Upgrade to v0.53 and support with-browser

[anton-iermolenko]

Adds support for usage of k6 timescaledb with browser-based load testing. Adds modified dashboard sample tuned for k6 browser metrics

[CLAassistant]

All committers have signed the CLA.

[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.}

[oleghalin]

Any updates on PR review?

[andrewslotin]

Hey, @anton-iermolenko! Thanks a lot for your contribution and apologies for the late answer. Could you elaborate on your use case and explain why these changes are needed?

[oleghalin]

Without this changes it's impossible to use timescale plugin with latest k6

K6 built on fixed version passed in gomod of this plugin

[anton-iermolenko]

Hey, @anton-iermolenko! Thanks a lot for your contribution and apologies for the late answer. Could you elaborate on your use case and explain why these changes are needed?

I needed to use K6 for browser-based load testing on multiple nodes with output into some storage. Starting k6 0.52.0 browser module is bundled by default, timeseries plugin not. Without these changes you cannot cook k6 which supports both. Dashboard sample added because latest version of k6 in browser mode spits Core Web Vitals differently into DB, so I had to rewrite queries pulling data from it to visualize in Grafana.

[andrewslotin]

@oleghalin, @anton-iermolenko, I see and upgrading to the latest k6 makes total sense. However, I'm not sure about adding the browser and Grafana dashboards though. We would prefer to keep extension code focused on providing the intended functionality, i.e. writing metrics to the TimescaleDB in this case, and avoid adding new use cases. You are more than welcome though to use grafana/xk6 as a image and add browser there.

[andrewslotin]

As per the comment above, I'd suggest to reduce these changes to upgrading the k6 version and move the dashboard and Dockerfile changes outside of the PR scope.

[andrewslotin]

By default xk6 uses the latest version of k6 required by extensions and since xk6-output-timescaledb is now locked to v0.53, this will be the lowest version used to build the binary. Is there any other reason to v0.53 specified here explicitly? Otherwise I'd suggest to drop this change.

[andrewslotin]

Also any reason to change the target directory to /usr/bin?