Update webpack-related deps, clean up some deps

[askoufis]

Not really sure why we had webpack-dev-server pinned. Also no idea how require-from-string got included in this PR from a while ago. It's currently unused, and AFAICT it never was used.

Also removed the assert dev dep and changed all imports to node:assert/strict in tests. There is one more usage of node assert in a fixture, but that can't be changed to node:assert because webpack doesn't know how to load the node: protocol. I think adding the NodeTargetPlugin may be the solution, but don't really want to investigate that right now.

• Removed the webpack-cli dev dep from sku, as it's not used. It's only used in the tests private package.
• Removed the traverse dep from sku as it was unused

[changeset-bot]

🦋 Changeset detected

Latest commit: 1fa0085

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
sku	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mrm007]

because webpack doesn't know how to load the node: protocol

It's the Babel plugin that needs to be configured to recognise node:assert/strict. You can verify it works OOTB with node:assert.
Webpack shouldn't even see the import, because Babel runs before Webpack.

[askoufis]

because webpack doesn't know how to load the node: protocol

It's the Babel plugin that needs to be configured to recognise node:assert/strict. You can verify it works OOTB with node:assert. Webpack shouldn't even see the import, because Babel runs before Webpack.

Babel unasssert is only run during production builds/prod dev server. So it doesn't work with regular sku start, which is the whole point.

[askoufis]

Also realised that webpack-cli wasn't used in sku as a dev dep, so I removed it.

[askoufis]

Found another unused dep, traverse.