Update dependency webpack-cli to v4

[dev-mend-for-github-com]

This PR contains the following updates:

Package	Type	Update	Change
webpack-cli (source)	dependencies	major	3.3.12 → 4.0.0

By merging this PR, the issue #11 will be automatically resolved and closed:

Severity	CVSS Score	Vulnerability	Reachability
High	7.5	CVE-2021-3807

---

Release Notes

webpack/webpack-cli (webpack-cli)

v4.0.0

Compare Source

Bug Fixes

• improve description of the --disable-interpret option (#​3364) (bdb7e20)
• remove the redundant utils export (#​3343) (a9ce5d0)
• respect NODE_PATH env variable (#​3411) (83d1f58)
• show all CLI specific flags in the minimum help output (#​3354) (35843e8)

Features

• failOnWarnings option (#​3317) (c48c848)
• update commander to v9 (#​3460) (6621c02)
• added the --define-process-env-node-env option
• update interpret to v3 and rechoir to v0.8
• add an option for preventing interpret (#​3329) (c737383)

BREAKING CHANGES

• the minimum supported webpack version is v5.0.0 (#​3342) (b1af0dc), closes #​3342
• webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
• webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
• remove the migrate command (#​3291) (56b43e4), closes #​3291
• remove the --prefetch option in favor the PrefetchPlugin plugin
• remove the --node-env option in favor --define-process-env-node-env
• remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
• the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

---

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

[dev-mend-for-github-com]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/Administration/Resources/app/administration/package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @vue/server-renderer@3.3.4
npm WARN Found: vue@3.3.4
npm WARN node_modules/vue3/node_modules/vue
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer overridden vue@"2.7.14" (was "3.3.4") from @vue/server-renderer@3.3.4
npm WARN node_modules/vue3/node_modules/@vue/server-renderer
npm WARN   @vue/server-renderer@"3.3.4" from vue3@3.3.4
npm WARN   node_modules/vue3
npm WARN   1 more (vue)
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: administration@1.0.0
npm ERR! notsup Not compatible with your version of node/npm: administration@1.0.0
npm ERR! notsup Required: {"node":"^18.0.0 || ^19.0.0 || ^20.0.0","npm":"^8.0.0 || ^9.0.0 || ^10.0.0"}
npm ERR! notsup Actual:   {"npm":"9.9.4","node":"v22.12.0"}

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-14T09_19_02_310Z-debug-0.log