refactor: remove vendored webpack versions, user must provider their own webpack tool from their node_modules

[gregmagolan]

My proposed pattern to use instead of vendoring the package.json & pnpm lock file for all versions of webpack.

This is a BREAKING CHANGE and should be pointed out in the release notes of the next release.

• remove A LOT of complexity from the repository
• solves the duplicate webpack found in node_modules directories problem
• reduces the maintenance burden of adding new versions of webpack to versions.bzl
• resolved the difficulty of getting rules_webpack onto bzlmod

After landing the same pattern would rolled out to rules_jasmine, rules_jest, rules_rollup & rules_terser which are all pre-1.0 still.

[kormide]

Nice 🦖 . So much cleaner.

[kormide]

Can we remove webpack_binary from the public defs now?

[jbedard]

What happens if a user doesn't have the 3 npm packages installed? Do they get any error message explaining it?

Is the webpack-dev-server package required if you don't use the webpack_devserver rule?

Overall seems way less complicated to me, especially when users have things like webpack plugin npm packages that need to mix with the vendored one etc.