221: Add basic error boundaries

[SebastianNowak01]

This pull request includes multiple changes to enhance error handling, refactor code, and update dependencies in the frontend project. The most important changes include the addition of error boundaries, refactoring of the UserMenu component to use React Query, and updating the package.json and package-lock.json files with new dependencies.

Error Handling Enhancements:

• Added react-error-boundary to handle errors gracefully in various components, including RateLimitStatus, UserMenu, About, and Dashboard pages. [1] [2] [3] [4] [5] [6] [7] [8]

Component Refactoring:

• Refactored UserMenu to use React Query for fetching user data and improved error handling. [1] [2]
• Replaced Box with Flex in Layout.tsx for better layout management.

Dependency Updates:

• Updated package.json and package-lock.json to include react-error-boundary. [1] [2] [3]

New Fallback Components:

• Added new fallback components for handling errors in ProfilePictureFallback, RateLimitStatusFallback, and UserMenuFallback. [1] [2] [3]

Schema Updates:

• Updated field names in various schemas in types.ts to follow camelCase convention. [1] [2] [3]

[deepsource-io]

Here's the code health analysis summary for commits b8c2ae5..a8e9e30. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Secrets	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗
Rust	✅ Success		View Check ↗
JavaScript	✅ Success	❗ 16 occurences introduced 🎯 8 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[Smixie]

For me everything is good.