fix(deps): update dependency @date-io/date-fns to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@date-io/date-fns	2.17.0 -> 3.0.0

---

Release Notes

dmtrKovalenko/date-io (@​date-io/date-fns)

v3.0.0

Compare Source

Breaking changes:

• chore(deps): bump date-fns to v3 by @​frsimond in https://github.com/dmtrKovalenko/date-io/pull/656
  This involves peer lib version upgrade please make sure that some underlying localised formats might be changed as well
• feat: Remove date-io/type definition by @​dmtrKovalenko in https://github.com/dmtrKovalenko/date-io/pull/657
  The type inference that doesn't work with modern typescript was removed. Please make sure to upgrade typescript to v5
• feat: Improve utils.date typescript typings by @​dmtrKovalenko in https://github.com/dmtrKovalenko/date-io/pull/658
  Changed signature of Utils.date and the underlying logic. Now if the value can't be parsed returns current date instead of null.

Other changes

• fix(js-jods): Proper support for date-only and time-only in mergeDateAndTime method by @​joshkel in https://github.com/dmtrKovalenko/date-io/pull/653

You can support the maintenance of this project by visiting https://github.com/sponsors/dmtrKovalenko. Your support will help us respond faster and deliver requested features. We extend our heartfelt thanks to our contributors and sponsors ❤️.

New Contributors

• @​frsimond made their first contribution in https://github.com/dmtrKovalenko/date-io/pull/656
• @​joshkel made their first contribution in https://github.com/dmtrKovalenko/date-io/pull/653

Full Changelog: dmtrKovalenko/date-io@v2.17.0...v3.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 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: client/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @date-io/date-fns@3.0.0
npm ERR! Found: date-fns@2.30.0
npm ERR! node_modules/date-fns
npm ERR!   date-fns@"2.30.0" from the root project
npm ERR!   peerOptional date-fns@"^2.25.0" from @mui/x-date-pickers@6.18.2
npm ERR!   node_modules/@mui/x-date-pickers
npm ERR!     @mui/x-date-pickers@"6.18.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional date-fns@"^3.2.0" from @date-io/date-fns@3.0.0
npm ERR! node_modules/@date-io/date-fns
npm ERR!   @date-io/date-fns@"3.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: date-fns@3.6.0
npm ERR! node_modules/date-fns
npm ERR!   peerOptional date-fns@"^3.2.0" from @date-io/date-fns@3.0.0
npm ERR!   node_modules/@date-io/date-fns
npm ERR!     @date-io/date-fns@"3.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/2024-04-03T12_12_58_435Z-eresolve-report.txt

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