fix(deps): update dependency @hookform/resolvers to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@hookform/resolvers (source)	^4.1.0 -> ^5.0.0

---

Release Notes

react-hook-form/resolvers (@​hookform/resolvers)

v5.0.1

Compare Source

Bug Fixes

• relax version constraint for react-hook-form 7.55.0 → ^7.55.0 (#​758) (6e88393)

v5.0.0

Compare Source

Features

• infer input/output types from schema (#​753) (6124c59)

BREAKING CHANGES

• Requires react-hook-form@7.55.0 or higher

Before
Prior to V5, some projects used manual types like

useForm<FormValues>();

After
With V5, the correct approach is:

useForm<Input, Context, Output>();
useForm<FormInputValues, Context, FormOutputValues>();

This update enables distinct outputs when utilizing features like transform from validation libraries.

ℹ️ The best approach is to let the types be inferred from your schema, rather than manually defining them.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 12:59 AM ( * 0 * * * ) in timezone Asia/Tokyo, 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]

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: mui-color-input@6.0.0
npm error Found: @mui/material@7.0.2
npm error node_modules/@mui/material
npm error   @mui/material@"^7.0.0" from the root project
npm error   peer @mui/material@"^5.15.14 || ^6.0.0 || ^7.0.0 || ^7.0.0-beta" from @mui/x-date-pickers@7.28.3
npm error   node_modules/@mui/x-date-pickers
npm error     @mui/x-date-pickers@"^7.27.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @mui/material@"^6.0.0" from mui-color-input@6.0.0
npm error node_modules/mui-color-input
npm error   mui-color-input@"^6.0.0" from the root project
npm error
npm error Conflicting peer dependency: @mui/material@6.4.11
npm error node_modules/@mui/material
npm error   peer @mui/material@"^6.0.0" from mui-color-input@6.0.0
npm error   node_modules/mui-color-input
npm error     mui-color-input@"^6.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-05-16T16_42_13_792Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-16T16_42_13_792Z-debug-0.log