Update Node.js version

[nfmohit]

Feature Description

We are currently running on a roughly older LTS of Node (14) and we should explore updating to the newer LTS (18) to benefit from the performance improvements and npm v7.

This came up while working on #5345 where https://github.com/browserslist/update-db isn't compatible with npm versions < 7.

This issue should include updating the browserslist-update-action to the latest version, see: https://github.com/google/site-kit-wp/pull/5883/files#r1004133133.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• .nvmrc is updated to use lts/jod version (22.x).
• Dependencies that don't support that version are updated to newer versions.

Implementation Brief

• Wait until Move js dependencies required for E2E tests into their own workspace #10013 Move js dependencies required for storybook into their own workspace #10091 Move js dependencies required to build assets into their own workspace #10092 Move js dependencies required for backstop tests into their own workspace #10093 Move js dependencies required for js tests into their own workspace #10094 are merged
• Update the version of Node to lts/jod in .nvmrc
• Do clean install using npm ci command and upgrade all dependencies that don't work with the new version
• Check all GitHub actions and fix them if any is broken due to version upgrade.

Test Coverage

• N/A

QA Brief

• Plugin should be thoroughly smoke-tested as this adjusts the build process of the plugin.

Changelog entry

• Update version of NodeJS used to build Site Kit.

[tofumatt]

A note here about something else we can improve in the code when we upgrade Node: https://github.com/google/site-kit-wp/pull/6514/files#diff-f4bce83c408f8dc8922d771b6e6148ca21c6b980d139be6df4cc15b4505b1f0fR27-R42

[kuasha420]

This is a fairly urgent upgrade now, as 14 completely lost all kind of support (even security patch) a month ago. cc @aaemnnosttv

[mxbclang]

@kuasha420 @aaemnnosttv Thanks for the flag! I can add this to Sprint 103; should this be upgraded from a P2?

[aaemnnosttv]

I think we can make it a P1 but it's not critical – Node is only something we use for builds and local development. The plugin still supports PHP 5.6 (just like WP core) which has long been EOL much longer 😄

[tofumatt]

I've left this as a 19 because it will likely involve E2E work and other unknowns, but I spent some time getting Node 18 builds working with many WordPress upgrades and a React upgrade—it does build in-browser and works without issue so far! 😄