chore(deps): update dependency copy-webpack-plugin to v12

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
copy-webpack-plugin	^11.0.0 -> ^12.0.0

---

Release Notes

webpack-contrib/copy-webpack-plugin (copy-webpack-plugin)

### [`v12.0.2`](https://togithub.com/webpack-contrib/copy-webpack-plugin/blob/HEAD/CHANGELOG.md#1202-2024-01-17) [Compare Source](https://togithub.com/webpack-contrib/copy-webpack-plugin/compare/v12.0.1...v12.0.2) ### [`v12.0.1`](https://togithub.com/webpack-contrib/copy-webpack-plugin/blob/HEAD/CHANGELOG.md#1201-2024-01-11) [Compare Source](https://togithub.com/webpack-contrib/copy-webpack-plugin/compare/v12.0.0...v12.0.1) ### [`v12.0.0`](https://togithub.com/webpack-contrib/copy-webpack-plugin/blob/HEAD/CHANGELOG.md#1200-2024-01-10) [Compare Source](https://togithub.com/webpack-contrib/copy-webpack-plugin/compare/v11.0.0...v12.0.0) ##### ⚠ BREAKING CHANGES - update `globby` to `14.0.0` - minimum supported `Node.js` version is `18.12.0` ([#​759](https://togithub.com/webpack-contrib/copy-webpack-plugin/issues/759)) ([a5b7d06](https://togithub.com/webpack-contrib/copy-webpack-plugin/commit/a5b7d06a051b7404b3300ed4d071b4948cb440f1))

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ 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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: imFile@1.0.7
npm ERR! Found: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.32.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.0.1" from @vue/eslint-config-standard@8.0.1
npm ERR! node_modules/@vue/eslint-config-standard
npm ERR!   dev @vue/eslint-config-standard@"^8.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-20T12_46_37_966Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-20T12_46_37_966Z-debug-0.log