fix(deps): update dependency swagger-ui-dist to v4.19.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
swagger-ui-dist	4.18.0 -> 4.19.1

---

Release Notes

swagger-api/swagger-ui (swagger-ui-dist)

v4.19.1: Swagger UI v4.19.1 Released!

Compare Source

Bug Fixes

• export standalone preset from the npm package (#​8906) (cdd0bdd), closes #​8163
• request-body: fix immutable prop types validation (#​8307) (07a08cd)

v4.19.0: Swagger UI v4.19.0 Released!

Compare Source

Bug Fixes

• oas3: fix deep linking for Callbacks (#​8691) (58b460d), closes #​8556

Features

• auth: persist cookie based apiKey in document.cookie (#​8689) (7ac9a8f), closes #​8683

Enhancements

• docker: update Dockerfile base image to nginx:1.24.0-alpine (#​8697) (da48ea1)

v4.18.3: Swagger UI v4.18.3 Released!

Compare Source

Bug Fixes

• response-body: remove download button when content is empty (#​8579) (cdfc4de)

v4.18.2: Swagger UI v4.18.2 Released!

Compare Source

Bug Fixes

• decode model schema name on model component (#​8400) (44e2700), closes #​5626
• oas3: expand Callback operation without browser error (#​8510) (cb15dbb), closes #​7465

v4.18.1: Swagger UI v4.18.1 Released!

Compare Source

Fixes

• reserve latest tag for swaggerapi/swagger-ui docker image for 4.x.y release channel

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 notice 
npm notice New major version of npm available! 8.19.4 -> 9.7.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.7.1>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @cucumber/[email protected]
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 [email protected]
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/[email protected]
npm ERR! node_modules/@cucumber/cucumber
npm ERR!   peerOptional @cucumber/cucumber@"^7.3.2 || ^8.0.0" from [email protected]
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/worker/c5a90f/d4fe16/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/worker/c5a90f/d4fe16/cache/others/npm/_logs/2023-06-12T19_15_28_604Z-debug-0.log

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[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: [email protected]
npm ERR! Found: @cucumber/[email protected]
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 [email protected]
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/[email protected]
npm ERR! node_modules/@cucumber/cucumber
npm ERR!   peerOptional @cucumber/cucumber@"^7.3.2 || ^8.0.0" from [email protected]
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_22_10_739Z-debug-0.log