feat: Driver Scheduling Integration — connect Driver model to core-api scheduling system

[roncodes]

Overview

This PR connects the FleetOps Driver model to the existing scheduling system in fleetbase/core-api, completing the scheduling integration described in issue #214. It is a prerequisite for the Intelligent Order Allocation Engine (PR to follow), which uses driver shift time_window data as hard constraints in the optimization solver.

---

Backend Changes

server/src/Models/Driver.php

• Added schedules() — MorphMany relationship (driver as polymorphic subject on Schedule)
• Added scheduleItems() — MorphMany relationship (driver as polymorphic assignee on ScheduleItem)
• Added activeShiftFor($date) — convenience method used by the AllocationPayloadBuilder to retrieve the driver's active shift and inject time_window constraints into the VROOM payload
• Added availabilities() — MorphMany relationship for time-off and preferred working hours
• Added required use statements for Schedule, ScheduleItem, ScheduleAvailability, MorphMany

server/src/Http/Controllers/Internal/v1/Traits/DriverSchedulingTrait.php (new)

Provides four scheduling endpoints as a trait applied to DriverController:

• scheduleItems(id, request) — GET /{id}/schedule-items with optional date range filter
• availabilities(id, request) — GET /{id}/availabilities with optional date range filter
• hosStatus(id) — GET /{id}/hos-status — computes daily and weekly hours from completed/in-progress shifts
• activeShift(id) — GET /{id}/active-shift — returns the driver's currently active shift

server/src/Http/Controllers/Internal/v1/DriverController.php

• Added use DriverSchedulingTrait

server/src/routes.php

• Registered four scheduling sub-routes under the internal drivers fleetbaseRoutes group

---

Frontend Changes

addon/components/driver/schedule.js (rewritten)

• Injects fetch, intl, store, driverScheduling, modalsManager, notifications
• loadDriverSchedule task: queries schedule-items via the driverScheduling service
• loadAvailability task: queries schedule-availability records via store
• loadHOSStatus task: calls /drivers/{id}/hos-status, suppresses 404 gracefully for drivers without HOS data
• addShift, editShift, deleteShift actions using modals/add-driver-shift and modals/driver-shift
• setAvailability, requestTimeOff, deleteAvailability actions using modals/set-driver-availability

addon/components/driver/schedule.hbs (rewritten)

• HOS Status panel — shows daily/weekly hours with compliance badge; hidden when hosStatus is null
• Upcoming Shifts panel — lists shifts with inline edit/delete buttons
• Availability & Time Off panel — lists availability restrictions with add/delete actions
• Styled with Fleetbase UI conventions (ContentPanel, Badge, Button, Tailwind)

addon/components/modals/add-driver-shift.{js,hbs} (new)

• Creates a ScheduleItem with assignee_type=driver
• Supports both single-driver mode (opened from driver panel) and multi-driver mode (opened from global scheduler) via hasManyDrivers computed property

addon/components/modals/driver-shift.{js,hbs} (new)

• Edits an existing ScheduleItem, pre-populates all fields from the passed item

addon/components/modals/set-driver-availability.{js,hbs} (new)

• Shared modal for both Set Availability (is_available=true) and Request Time Off (is_available=false) flows

addon/services/driver-actions.js

• Added Schedule tab (component: 'driver/schedule') to the driver view panel tabs array

addon/controllers/operations/scheduler/index.js

• Added driverAvailabilities tracked property
• Enhanced events computed to render unavailable availability records as FullCalendar background events (red-300) so dispatchers can see time-off blocks at a glance
• Added loadDriverAvailabilities task
• switchViewMode('drivers') now also calls loadDriverAvailabilities
• addDriverShift modal title and button text now use intl.t()

---

Relationship to Allocation Engine

The activeShiftFor() method on the Driver model is the key integration point for the upcoming Allocation Engine PR. The AllocationPayloadBuilder will call this method for each candidate driver and inject the shift start_at/end_at as a VROOM time_window constraint, ensuring the solver cannot assign a route that would cause a driver to exceed their scheduled hours.

Refs: #214