[fix] fix all cve warnings

[allansson]

This PR fixes all the CVE warnings when running ´trivyandnpm audit` on the repo.

The critical CVE was easy to fix. We just needed to upgrade babel to the latest version and it went away.

The other warnings were caused by an old version of ava, and that proved to be trickier to fix. The old version had support for mixing ESM and CJS, but that was dropped in favor of native esm support in node. But that has some problems:

1. NODE_PATH doesn't work with ESM, so all paths would have to be converted to relative in the test suite.
2. Node detects the module type based on the file extension and the type property in package.json: if type is "module" CJS modules need to have the extension .cjs and vice versa.

In the end, the simplest solution was to just convert all the import statements in the test suite to require statements.

How to test

1. Install trivy
2. Run trivy fs . --include-dev-deps in the repository
3. Run npm audit in the reposity
4. Run the CLI on some HAR file

Expected result

There should be no CVEs.

[w1kman]

CR: I'm a bit sceptical against installing "D".

FYI: Since we are pushing a docker image on build (which is scanned by Grafana using trivy). I ran trivy image har-to-k6:local, which resulted in Total: 57 (UNKNOWN: 0, LOW: 50, MEDIUM: 5, HIGH: 1, CRITICAL: 1)

Not asking you to fix the image vulnerabilities, just pointing out that they are subjected to show up when grafana scans the docker image.

[w1kman]

Why?
This package has been deprecated

[allansson]

A guess: npm install D 😅

[allansson]

I've updated the Dockerfile to use node:20-alpine to minimize the CVEs to 2 medium ones. It also shrinks the image by 60 MB.

D has been removed.

I also noticed a warning that babel-eslint was no longer updated, so I switched to @babel/eslint-parser to make any future updates easier.

[w1kman]

LGTM 👌🏻

[2Steaks]

Tested with success and no warnings 👍