chore(deps): update dependency @types/express to v4.17.23

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/express (source)	4.16.1 -> 4.17.23

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (81cc19f) 92.72% compared to head (3714132) 9.45%.

❗ Current head 3714132 differs from pull request most recent head ef04b78. Consider uploading reports for the commit ef04b78 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #44       +/-   ##
==========================================
- Coverage   92.72%   9.45%   -83.27%     
==========================================
  Files           3       3               
  Lines          55     148       +93     
  Branches        8      25       +17     
==========================================
- Hits           51      14       -37     
- Misses          4     134      +130     

see 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/marked
npm ERR!   marked@"^0.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR! node_modules/marked-terminal
npm ERR!   marked-terminal@"^3.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/marked
npm ERR!   peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR!   node_modules/marked-terminal
npm ERR!     marked-terminal@"^3.1.1" 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/worker/20ccbf/1bf0b4/cache/others/npm/_logs/2023-11-07T04_21_44_171Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/20ccbf/1bf0b4/cache/others/npm/_logs/2023-11-07T04_21_44_171Z-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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/marked
npm ERR!   marked@"^0.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR! node_modules/marked-terminal
npm ERR!   marked-terminal@"^3.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/marked
npm ERR!   peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR!   node_modules/marked-terminal
npm ERR!     marked-terminal@"^3.1.1" 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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-06-07T06_38_32_484Z-debug-0.log