chore: Update dependencies and configuration

[AvivAbachi]

• @mui/x-date-pickers - complext changes

[github-actions]

Preview: https://s3.amazonaws.com/noam-gaash.co.il/21165134455/open-bus/1569/index.html
Preview Storybook: https://s3.amazonaws.com/noam-gaash.co.il/21165134455/open-bus/1569/storybook/index.html
Test Report (if available): 'https://s3.amazonaws.com/noam-gaash.co.il/21165134455/open-bus/7bd174c16affbe15def459ce41ffa9c86abd6792/test-results/index.html'

[NoamGaash]

@claude can you solve conflicts?

[claude]

Claude finished @NoamGaash's task in 2m 33s —— View job

---

Resolving merge conflicts ✅

• Check current git status and identify any conflicts
• Fetch latest changes from origin/main
• Attempt to merge origin/main into current branch
• Resolve conflicts in 18 files (kept PR's dependency updates, added .envrc to .gitignore)
• Commit and push the merge

Summary: Successfully resolved all merge conflicts! The issue was caused by a shallow git clone treating the branches as unrelated histories. I resolved 18 files by:

1. Keeping the PR's dependency updates - This PR is specifically for updating dependencies, so I preserved all the version updates in package.json and package-lock.json
2. Added .envrc to .gitignore - The only actual change from origin/main was adding .envrc to the gitignore file, which I incorporated

The merge commit has been pushed to the branch. The CI checks will verify that everything builds and passes tests correctly.

Note: I couldn't run local verification checks (npm install, lint, build) due to the Node.js version in the CI environment (v20.19.6) being incompatible with the updated package.json requirement (node>=22.0.0). The CI pipeline should handle this with the correct Node version.

--- | Branch