Fix bug with playwright

[JoshuaSBrown]

PR Description

Fixes the CI where playwright dependencies have changed.

See #1342

Tasks

• - A description of the PR has been provided, and a diagram included if it is a new feature.
• - Formatter has been run
• - CHANGELOG comment has been added
• - Labels have been assigned to the pr
• - A reviwer has been added
• - A user has been assigned to work on the pr
• - If new feature a unit test has been added

Summary by Sourcery

CI:

• Updates the Node.js version to 18 in the end-to-end web tests CI configuration.

Summary by Sourcery

Fixes a bug with Playwright by updating the end-to-end test configuration to use Node.js v18 and ensuring the correct environment is set up for Playwright to run.

CI:

• Updates the end-to-end test CI configuration to install and use Node.js v18.
• Ensures the NVM directory is correctly set up in the CI environment.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Node.js version used in the end-to-end web tests CI configuration to version 18. This is accomplished by adding NVM to the CI environment, installing Node.js 18, and then using it.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updates the Node.js version used in the end-to-end web tests CI configuration to version 18.	Adds NVM_DIR environment variable. Installs Node.js version 18 using nvm. Uses Node.js version 18 using nvm.	.gitlab/end_to_end.yml

Possibly linked issues

• [CI, Testing, Playwright] - bug in ci job using browser with playwright #1342: The PR fixes the error in the CI job with playwright by updating the node version used.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @JoshuaSBrown - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a specific Node.js version instead of a floating one to avoid unexpected behavior.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

Hey @JoshuaSBrown - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a specific Node.js version like 18.19.0 instead of just 18 to avoid unexpected behavior from patch updates.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[t-ramz]

Are we on 18 or 20?

[JoshuaSBrown]

It doesn't really matter for playwright, playwright runs outside of any of the other node modules. Though it would be better to keep things consistent.

[AronPerez]

Would be 20 with #1336 (comment) but not yet

[t-ramz]

Understood