chore(deps): update dependency @types/marked to v5

[json-derulo]

This PR contains the following updates:

Package	Type	Update	Change
@types/marked (source)	devDependencies	major	^4.0.8 -> ^5.0.0

---

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 has been generated by Renovate Bot.

[json-derulo]

⚠ 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: ngx-markdown@16.0.0
npm ERR! Found: @types/marked@5.0.1
npm ERR! node_modules/@types/marked
npm ERR!   dev @types/marked@"^5.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @types/marked@"^4.3.0" from ngx-markdown@16.0.0
npm ERR! node_modules/ngx-markdown
npm ERR!   ngx-markdown@"^16.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/marked@4.3.1
npm ERR! node_modules/@types/marked
npm ERR!   peer @types/marked@"^4.3.0" from ngx-markdown@16.0.0
npm ERR!   node_modules/ngx-markdown
npm ERR!     ngx-markdown@"^16.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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-08-01T21_13_22_562Z-eresolve-report.txt

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

[json-derulo]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.