Lock file maintenance

[renovate]

This PR contains the following updates:

Update
lockFileMaintenance

🔧 This Pull Request updates package.json lock files to use the latest dependency versions.

---

Renovate configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.

[sarah-clements]

@edmorley Why do you think this keeps exceeding the bundle size (I may be missing a point you made in #4586)?

[edmorley]

React had another point release, so there's another dupe:
https://github.com/mozilla/treeherder/pull/4608/files#diff-8ee2343978836a779dc9f8d6b794c3b2R7786

Until yarn fixes yarnpkg/yarn/issues/3967 or Renovate adds a "consolidate dupes" workaround (perhaps worth filing an issue against Renovate to see if they'd be willing to use one of the workaround packages mentioned in the Yarn issue?) the dupes are unavoidable, and either need manual removal each time React gets an update, or else the threshold bumped up such that it's not exceeded in such cases (with the understanding that the dupes will still exist until the React PR + lockfile PRs are both merged after each release).

[sarah-clements]

@edmorley Aghhh, the bot keeps keeps closing the branch! I realized I accidentally merged #4645 that also had a dupe and there are merge conflicts when I try to reopen this branch so I wonder if that is why it keeps closing. I didn't plan out the sequencing for approving these dep upgrades very well... this yarn bug is so frustrating :(

[edmorley]

@edmorley Aghhh, the bot keeps keeps closing the branch!

@rarkins I don't suppose you know what's happening here? (renovatebot/renovate/issues/3018)