chore(deps): update dependency jasmine-core to ~5.4.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jasmine-core (source)	~5.0.1 -> ~5.4.0

---

Release Notes

jasmine/jasmine (jasmine-core)

v5.4.0

Compare Source

Please see the release notes.

v5.3.0

Compare Source

Please see the release notes.

v5.2.0

Compare Source

v5.1.2: 5.1.2

Compare Source

Please see the release notes.

v5.1.1: 5.1.1

Compare Source

Please see the release notes.

v5.1.0: 5.1.0

Compare Source

Please see the release notes.

---

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 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: @agm/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^15.2.10" from the root project
npm ERR!   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/[email protected]
npm ERR!   node_modules/@angular/cdk
npm ERR!     @angular/cdk@"^15.2.9" from the root project
npm ERR!     peer @angular/cdk@"15.2.9" from @angular/[email protected]
npm ERR!     node_modules/@angular/material
npm ERR!       @angular/material@"^15.2.9" from the root project
npm ERR!       1 more (ngx-ui-tour-md-menu)
npm ERR!     1 more (ngx-ui-tour-md-menu)
npm ERR!   17 more (@angular/forms, @angular/material, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm ERR! node_modules/@agm/core
npm ERR!   @agm/core@"^3.0.0-beta.0" from the root project
npm ERR!   peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm ERR!   node_modules/@agm/snazzy-info-window
npm ERR!     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm ERR!   node_modules/@agm/core
npm ERR!     @agm/core@"^3.0.0-beta.0" from the root project
npm ERR!     peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm ERR!     node_modules/@agm/snazzy-info-window
npm ERR!       @agm/snazzy-info-window@"^3.0.0-beta.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/2023-12-11T17_05_27_035Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-11T17_05_27_035Z-debug-0.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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @agm/[email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/common
npm error   @angular/common@"^15.2.10" from the root project
npm error   peer @angular/common@"^15.0.0 || ^16.0.0" from @angular/[email protected]
npm error   node_modules/@angular/cdk
npm error     @angular/cdk@"^15.2.9" from the root project
npm error     peer @angular/cdk@"15.2.9" from @angular/[email protected]
npm error     node_modules/@angular/material
npm error       @angular/material@"^15.2.9" from the root project
npm error       1 more (ngx-ui-tour-md-menu)
npm error     1 more (ngx-ui-tour-md-menu)
npm error   17 more (@angular/forms, @angular/material, ...)
npm error
npm error Could not resolve dependency:
npm error peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error node_modules/@agm/core
npm error   @agm/core@"^3.0.0-beta.0" from the root project
npm error   peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error   node_modules/@agm/snazzy-info-window
npm error     @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Conflicting peer dependency: @angular/[email protected]
npm error node_modules/@angular/common
npm error   peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm error   node_modules/@agm/core
npm error     @agm/core@"^3.0.0-beta.0" from the root project
npm error     peer @agm/core@"3.0.0-beta.0" from @agm/[email protected]
npm error     node_modules/@agm/snazzy-info-window
npm error       @agm/snazzy-info-window@"^3.0.0-beta.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-12T18_21_56_505Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-12T18_21_56_505Z-debug-0.log