updated react and react-dom

[0x00b1]

Hi, @JackUrb! I needed to update react and react-dom for the compression task. Let me know if this works.

cc: @mmuckley

[JackUrb]

@pringshia any thoughts on how we deal with react versions in Mephisto? Has been an issue for other projects as well

[pringshia]

This PR includes quite a bit of package version updates which I'm hesitant on merging right away, as there could be unintended behavior, the currently breaking tests aside. To back up a bit, what part of the prior version of react / react-dom was causing issues? Also I would advise to break down the PR to introduce the updates across the various packages incrementally instead of all-at-once.

[0x00b1]

To back up a bit, what part of the prior version of react / react-dom was causing issues? Also I would advise to break down the PR to introduce the updates across the various packages incrementally instead of all-at-once.

Lack of useDeferredValue and useTransition. Also the ability to use @mui/material 5.10.4.

[pringshia]

This is causing tests to fail due to the following issue: actions/setup-node#317

[pringshia]

Given the node version bump in the GH runner, seems like we'll also need to update yarn to version 3.2.2+ to fix the issue seen here:

➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR node:internal/errors:477
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     ErrorCaptureStackTrace(err);
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     ^
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR 
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR Error [ERR_LOADER_CHAIN_INCOMPLETE]: "file:///home/runner/work/Mephisto/Mephisto/.pnp.loader.mjs 'resolve'" did not call the next hook in its chain and did not explicitly signal a short circuit. If this is intentional, include `shortCircuit: true` in the hook's return.
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at new NodeError (node:internal/errors:387:5)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at ESMLoader.resolve (node:internal/modules/esm/loader:[85](https://github.com/facebookresearch/Mephisto/runs/8275528832?check_suite_focus=true#step:9:89)2:13)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at async ESMLoader.getModuleJob (node:internal/modules/esm/loader:431:7)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at async Promise.all (index 0)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at async ESMLoader.import (node:internal/modules/esm/loader:533:24)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at async loadESM (node:internal/process/esm_loader:91:5)
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR     at async handleMainPromise (node:internal/modules/run_main:65:12) {
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR   code: 'ERR_LOADER_CHAIN_INCOMPLETE'
  ➤ YN0000: │ @parcel/watcher@npm:2.0.4 STDERR }
  ➤ YN0009: │ @parcel/watcher@npm:2.0.4 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-d4a4833f/build.log)

[pringshia]

Following up on this, I think you should just be able to relax the peerDependency requirement for mephisto-task instead of doing such a broad version bump across the codebase. For example: https://github.com/palantir/blueprint/blob/b0d500511217db6590e86ccb9627385b4fd153a5/packages/core/package.json#L63-L64

[pringshia]

Resolved with #905