Update dependency @types/react-router to v5.1.20

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react-router (source)	5.1.16 -> 5.1.20

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, 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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @ionic/react-hooks@0.0.8
npm ERR! Found: @capacitor/core@2.4.7
npm ERR! node_modules/@capacitor/core
npm ERR!   @capacitor/core@"2.4.7" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR! node_modules/@ionic/react-hooks
npm ERR!   @ionic/react-hooks@"0.0.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @capacitor/core@1.3.0
npm ERR! node_modules/@capacitor/core
npm ERR!   peer @capacitor/core@"~1.3.0" from @ionic/react-hooks@0.0.8
npm ERR!   node_modules/@ionic/react-hooks
npm ERR!     @ionic/react-hooks@"0.0.8" 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-03-17T01_52_01_239Z-eresolve-report.txt

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