chore: major dev maintenance for RUM agent

[devcorpio]

Summary

Node and npm

• Node.js 18 support
• npm >= 8 support + legacy-peer-deps=true in a new .npmrc. This allows us to update things gradually. In a nutshell, that flag makes npm behave like it was doing in versions 4-6.

E2E Developer Experience

• updated webdriverio and wdio dependencies to the latest one. Mainly for improving the reporting and exit code behaviour, more info:
  - [🐛 Bug]: onComplete Hook Provides an exit code of 1 When Test Suite Passes When Using Cucumber Tag Expression Due to Error in onRunnerStart hook of wdio-video-reporter webdriverio/webdriverio#9440
  - [🐛 Bug]: if session initialisation failed, the result of the test is not be part of the reporter webdriverio/webdriverio#8307 (we are victims of this one every now and then and it's so frustrating, it's so time-consuming)
• all E2E tests are now also working with the new webdriver async mechanism https://webdriver.io/docs/async-migration/
• all of them keep working perfectly 🎉 , you can see that in the CI pipeline of this commit. The commits after that were more focused on making sure that benchmarking, load-testing, and dry-run-release also worked properly.

Webpack compatibility with Node 18

• Make webpack and Node.18 compatible (nodejs 17: digital envelope routines::unsupported webpack/webpack#14532).
  - our webpack config uses now the first solution(xxhash64) offered by the creator of webpack. More info here
  - for the angular package the second solution(--openssl-legacy-provider flag) is the one applied since updatingangular-clidependencies is not an option given the huge the task is.

Final thoughts

This lack of maintenance was causing several DX problems and with the passing of time to fix this was becoming more and more difficult because of the enormous gap between the versions.

Possible future maintenance candidates: lerna, angular cli, benchmarking, and load-testing (the last two still use Node 14. Adapting Playwright and its related dependencies to work with Node.js 18 is not a piece of cake, maybe this should be the one to do first because the source from where we installed Node.js 14 is going to become inactive sooner rather than later, you can see that warning in the logs), etc. No need to rush though, it can be done gradually since this PR now solves the main blockers we had.

[vigneshshanmugam]

LGTM 🎉

[vigneshshanmugam]

Given that you have set the NODE_OPTIONS on benchmark scripts, can you remove the hardcoded version here?

[devcorpio]

Actually, I will let the hardcoded version here and remove the NODE_OPTIONS from benchmark scripts until we decide to apply this update to the benchmarking, too. My surprise was big when I saw that this dockerfile is also built in a different step (which provides the Node 18 version) of the CI: https://github.com/elastic/apm-agent-rum-js/actions/runs/6284894505/job/17066717885

EDIT: In fact, thinking more about this, I would let things are they are:

• Having the comments will help to have context
• Once we do the docker update we will need to change the installation setup anyway (like we do in the puppeteer one, so the hardcoded 14 will go away anyway)

And, just for more visibility, this is the capture of the Node.js 14 warning I mentioned in the PR's description:

[vigneshshanmugam]

Did you talk to the Robots team about using this custom image?

The other option is to fix our obserability ci image which is from our shared pipeline.

[devcorpio]

I didn't mention anything explicitly because, in the other image, we were using ubuntu:bionic which is another "custom" image.

I can share this with Robots, and discuss if it would be required to align approaches in future iterations

[amannocci]

In my opinion, It's fine to use any distro base image from a trusted provider.

[amannocci]

LGTM