Upgrade Webpack dependencies to resolve security advisories

[aduth]

🛠 Summary of changes

Upgrades Webpack-related dependencies to their latest versions.

Initially this was targeted at webpack-dev-server, which has some related open security advisories (GHSA-wr3j-pwj9-hqq6, GHSA-rv95-896h-c2vc, GHSA-cxjh-pqwp-8mfp), but I decided to upgrade a few others since webpack-dev-server at least required a version bump of webpack-cli to >5.0.

Related CHANGELOG:

• https://github.com/webpack/webpack-dev-server/blob/master/migration-v5.md
• https://github.com/webpack/webpack-cli/releases/tag/webpack-cli%405.0.0
• https://github.com/webpack/webpack/releases
• https://github.com/webdeveric/webpack-assets-manifest/releases

These security updates don't block builds since we only check for dependencies installed in production environments, but it's prudent to resolve them, and minimizes noise in the GitHub UI and push messages..

📜 Testing Plan

1. yarn install
2. make run
3. Visit http://localhost:3000
4. Observe no errors in the browser or in the Terminal output

[zachmargolis]

is it a valuable test to hardcode the specific files? would it make sense to have like a count + regex approach?

[aduth]

I'll check again in the morning if there's a strong reason to test them specifically. I think I wasn't expecting the suffix to change all that often since it's meant to be deterministic, but this isn't the first time I've had to update these as part of a version upgrade.

[aduth]

I updated this in 6452166 to be hopefully more resilient to these sorts of deterministic ID changes.