AirTrack BugTracker V2

When adding a new aircraft with a user-entered sighting date/time, First_Sighted was stored as naive AEST local time. Aircraft_Updated is stored as UTC. The display layer converts both +10h, causing First_Sighted to appear 10 hours ahead — showing a future date when the sighting was entered on the same day as entry. Fix: add_aircraft_routes.py now converts the user-entered sighting datetime from Australia/Sydney to UTC before storing (using ZoneInfo + astimezone). Four existing affected records corrected in DB via CONVERT_TZ SQL update.