Upgrading additional packages

[wjrosa]

Fixes STRIPE-696
Base PR #4264

Changes proposed in this Pull Request:

As part of the Node upgrade project, this PR upgrades additional NPM packages to match the main PR: cross-env, mkdirp, and rimraf.

• cross-env: allows usage of environment variables in commands
• mkdirp: directory creation
• rimraf: file deletion

We are also removing the chromedriver package, as we don't need it.

Testing instructions

• Checkout and build this branch on your test environment (dev/upgrading-additional-packages)
• Check if the frontend tests are still passing

---

• Covered with tests (or have a good reason not to test in description ☝️)
• Tested on mobile (or does not apply)

Changelog entry

• This Pull Request does not require a changelog entry. (Comment required below)

Changelog Entry Comment

Comment

Post merge

• Added testing instructions to the Release Testing Instructions wiki page (or does not apply)
• Added the needs docs label (or does not apply)
• Included this PR in the Release Thread scope (or does not apply)

[wjrosa]

Hey @diegocurbelo! Would you remember why it was necessary to add the ajv and wait-on packages to the main PR? Just double-checking if they are really necessary.

[wjrosa]

I went ahead and removed both packages. The main PR works just fine. So I think it is safe to remove them.

[diegocurbelo]

Hey @diegocurbelo! Would you remember why it was necessary to add the ajv and wait-on packages to the main PR? Just double-checking if they are really necessary.

It was because a couple of packages used different (and incompatible) versions of those two dependencies, and the npm resolver failed to find a version that worked for all of them; it might not be needed anymore.

[diegocurbelo]

The updated versions work, tests pass, and Woorelease generated the package correctly (including the build folder); both flows use rimraf and cross-env.

chromedriver: for e2e tests

We are using Playwright for the E2E tests, which does not require chromedriver.

[wjrosa]

That's good to know, Diego! Thank you. I removed the chromedriver package in 5c9f161. And everything seems to be working just fine indeed.

[daledupreez]

The changes LGTM, and both e2e and JS tests are looking good.