Update dependency jasmine-spec-reporter to v7

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jasmine-spec-reporter	~5.0.0 -> ~7.0.0

---

Release Notes

bcaudan/jasmine-spec-reporter (jasmine-spec-reporter)

### [`v7.0.0`](https://togithub.com/bcaudan/jasmine-spec-reporter/blob/HEAD/CHANGELOG.md#700) [Compare Source](https://togithub.com/bcaudan/jasmine-spec-reporter/compare/v6.0.0...v7.0.0) #### Bugfix - 'SpecReporter' is not assignable to type 'Reporter | CustomReporter' [#​588](https://togithub.com/bcaudan/jasmine-spec-reporter/pull/588) #### Breaking change Update signature of `CustomReporterResult` to fix collision with new jasmine properties **Before:** ```ts export interface CustomReporterResult extends jasmine.CustomReporterResult { duration?: string } ``` **Now:** ```ts export interface CustomReporterResult extends jasmine.CustomReporterResult { _jsr?: { formattedDuration?: string } } ``` ### [`v6.0.0`](https://togithub.com/bcaudan/jasmine-spec-reporter/blob/HEAD/CHANGELOG.md#600) [Compare Source](https://togithub.com/bcaudan/jasmine-spec-reporter/compare/v5.0.2...v6.0.0) #### Feature - Use colors/safe [#​538](https://togithub.com/bcaudan/jasmine-spec-reporter/pull/538) #### Breaking change String prototype does not contain color properties anymore, colors must now be applied with the new `theme` component available as a field in [custom display processors](docs/customize-output.md). **Before:** ```ts class MyProcessor extends DisplayProcessor { public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string { return 'OK '.successful + log } } ``` **Now:** ```ts class MyProcessor extends DisplayProcessor { public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string { return this.theme.successful('OK ') + log } } ```

---

Configuration

📅 Schedule: Branch creation - "after 8am and before 5pm on saturday" (UTC), 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[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 could not resolve
npm ERR! 
npm ERR! While resolving: delta@1.14.6
npm ERR! Found: @angular/animations@17.3.4
npm ERR! node_modules/@angular/animations
npm ERR!   @angular/animations@"17.3.5" from the root project
npm ERR!   peerOptional @angular/animations@"17.3.4" from @angular/platform-browser@17.3.4
npm ERR!   node_modules/@angular/platform-browser
npm ERR!     @angular/platform-browser@"17.3.5" from the root project
npm ERR!     peer @angular/platform-browser@"17.3.4" from @angular/forms@17.3.4
npm ERR!     node_modules/@angular/forms
npm ERR!       @angular/forms@"17.3.5" from the root project
npm ERR!     2 more (@angular/platform-browser-dynamic, @angular/router)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @angular/animations@"17.3.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/core@17.3.5
npm ERR! node_modules/@angular/core
npm ERR!   peer @angular/core@"17.3.5" from @angular/animations@17.3.5
npm ERR!   node_modules/@angular/animations
npm ERR!     @angular/animations@"17.3.5" 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-04-27T15_59_44_137Z-debug-0.log