chore(deps): update angular-cli monorepo to v15.2.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@angular-devkit/build-angular	15.2.2 -> 15.2.11
@angular/cli	15.2.2 -> 15.2.11

---

Release Notes

angular/angular-cli (@​angular-devkit/build-angular)

v15.2.11

Compare Source

@​angular-devkit/build-angular

Commit	Type	Description
c6feb0bb0	fix	update webpack-dev-middleware to 6.1.2

v15.2.10

Compare Source

@​angular-devkit/build-angular

Commit	Type	Description
05213c95b	fix	update dependency postcss to v8.4.31

v15.2.9

Compare Source

@​angular/cli

Commit	Type	Description
f36e38a91	fix	update direct semver dependencies to 7.5.3

v15.2.8

Compare Source

@​angular/cli

Commit	Type	Description
069dcdf0c	docs	improve wording in doc command version description

v15.2.7

Compare Source

@​angular/cli

Commit	Type	Description
f4a6dac87	fix	process keeps running when analytics are enabled
f9b2fb1c4	perf	register CLI commands lazily

@​schematics/angular

Commit	Type	Description
d9aefd6da	fix	replace vscode launch type from pwa-chrome to chrome

v15.2.6

Compare Source

@​schematics/angular

Commit	Type	Description
f0b257ef4	fix	ignore hidden directories when running browserlist migration

v15.2.5

Compare Source

@​angular/cli

Commit	Type	Description
db173d7ed	fix	collect tech information

Special Thanks

Alan Agius

v15.2.4

Compare Source

@​angular-devkit/build-angular

Commit	Type	Description
f74bfea24	fix	update webpack dependency to 5.76.1

Special Thanks

Alan Agius

v15.2.3

Compare Source

@​angular-devkit/build-angular

Commit	Type	Description
a93680585	fix	correct wrap ES2022 classes with static properties

Special Thanks

Alan Agius and Paul Gschwendtner

---

Configuration

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

🚦 Automerge: Enabled.

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

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

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: protractor-cucumber-framework@9.0.0
npm ERR! Found: @cucumber/cucumber@9.0.0
npm ERR! node_modules/@cucumber/cucumber
npm ERR!   dev @cucumber/cucumber@"9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @cucumber/cucumber@"^7.3.2 || ^8.0.0" from protractor-cucumber-framework@9.0.0
npm ERR! node_modules/protractor-cucumber-framework
npm ERR!   dev protractor-cucumber-framework@"9.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @cucumber/cucumber@8.11.1
npm ERR! node_modules/@cucumber/cucumber
npm ERR!   peerOptional @cucumber/cucumber@"^7.3.2 || ^8.0.0" from protractor-cucumber-framework@9.0.0
npm ERR!   node_modules/protractor-cucumber-framework
npm ERR!     dev protractor-cucumber-framework@"9.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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