ci(deps): dedupe yarn.lock, add check for dupes

[agilgur5]

Motivation

Use as few duplicates of dependencies as possible, reducing install size, memory usage, and bundle size

• See also https://github.com/atlassian/yarn-deduplicate#why-is-this-necessary and a PR from a repo I used to maintain: deps: add deduplicate script and apply yarn-deduplicate jaredpalmer/tsdx#683
• Removes 700+ lines from the yarn.lock by condensing deps

Modifications

• add a deduplicate script that uses yarn-deduplicate
• run deduplicate during make lint and UI CI
  • I added this as another one-liner in make lint b/c that was honestly much more readable than trying to do multi-line shell conditionals inside of a Makefile (which require \ and ; as they get interpreted as a single line)
• run deduplicate once and commit the results
  • double-checked 50%+ of these automated changes and they all look good to me

similar to a commit I made in a library I maintained a few years ago: jaredpalmer/tsdx@22133ce (part of jaredpalmer/tsdx#683)

Also, upgrade ts-loader to v8.4.0

• To support TS v4.7+ per the changelog
  • TS v4.6 was deduped. Previously there were two versions of TS being used by the build chain -- which itself could lead to some inconsistencies
• ts-loader v8's only breaking change was to no longer support TS <3.6
  • ts-loader v9 requires Webpack v5, so cannot bump to that yet (see also build(ui): upgrade to Webpack v5 + upgrade loaders + plugins #11628)

Verification

Ran the new make lint: confirmed it worked and did not make an additional diff.
Spot check on UI render was ok.
CI checks pass

Notes to Reviewers

This will likely merge conflict hard with a few my other open UI deps PRs, so it probably makes more sense to merge those first and then update this PR after those are all merged

[agilgur5]

Huh Prod UI build is failing on a ts-loader error. Was able to reproduce that locally, but it doesn't seem to occur in dev mode probably because type-checking is off.

That error suggests that one of the deps was relying on an outdated version of TS

[agilgur5]

Ah yep, TS 4.6 was deduped and ts-loader needs an update to support TS 4.7+.
(For reference, TS does not follow SemVer, so there can be breaking changes in minors like this one)

[terrytangyuan]

Can we combine this with other similar PRs?

[agilgur5]

So all 3 (#11641, #11630, and this one) are technically independent of each other.
In particular, this is the only one that massively merge conflicts when there's a dep change, the other two can be merged pretty cleanly. Pretty sure both of those can be merged right now.

[agilgur5]

One E2E test flake (I believe I've seen this one before too from a quick glance).
And unit tests failed on something completely unrelated in Go code -- that looks like potentially a race condition or something in the test? (it tried running both the dummy metrics server and the real one simultaneously)

[agilgur5]

Geh, some other PR ended up merge conflicting as well 😭 Possibly #11678.

Rebased on top