feat(drivers): Add routes to create and manage drivers

[timderes]

Add new routes and views to support creating, viewing, and managing drivers within the application.

This feature introduces a dedicated drivers module that allows users to:

• Create new drivers with relevant personal and club information
• View a list of existing drivers
• Edit and update driver details
• Manage driver data in the context of trainings and events (Jugendkartslalom / Superkartslalom)
• Add diagramms and statistics for each drivers

The goal is to establish a consistent and scalable structure for driver management that integrates with the existing database layer and UI patterns (Mantine forms, notifications, etc.).

Todos

• Create driver database schema (Dexie / database layer)
• Implement CRUD functions for drivers (create, read, update, delete)
• Add route for driver list view (e.g. /drivers)
• Add route for creating a new driver (e.g. /drivers/new)
• Build driver form hook (similar to useClubForm)
• Implement driver form UI (Mantine useForm, validation, etc.)
• Add edit functionality for existing drivers
• Handle form validation and error states
• Add success/error notifications
• Integrate driver selection into trainings/events workflow
• Ensure driver is linked to a club (if applicable)
• Add translations (common, driver namespaces)
• Add basic logging (electron-log)
• Consider adding UUID generation for drivers
• Optional: Add search/filter to driver list
• Optional: Add pagination or virtualization for large datasets

---

Notes

• Follow existing patterns from the club module (useClubForm, database structure, notifications)
• Keep form handling consistent (Mantine uncontrolled mode unless strong reason otherwise)
• Ensure future extensibility for competition-specific data (e.g. classes, rankings)