Show takeoff and landing events in each location's local timezone on Flight History

Problem:

On the Flight History page, takeoff and landing event timestamps are shown in a single timezone. For operators flying across timezones, this hides the actual local time at which events occurred at each location — which is what most operational and journey log workflows need. A single TZ annotation per row is insufficient: takeoff and landing can be in different timezones, and the engine/blocks events at each location must follow the same TZ as the corresponding takeoff or landing event.

Desired outcome:

Operators want to see takeoff- and landing-related events in the local timezone of the respective location, with clear labelling of which timezone applied at each end of the flight.

Proposed change:

Add a "Local times" toggle / checkbox on the Flight History page. When enabled, two new columns are inserted: one before the takeoff group (engine on / blocks off / take off) showing the TZ code at the takeoff location, and one before the landing group (landing / blocks on / engine off) showing the TZ code at the landing location. Timestamps in each group are rendered in the local timezone of that location.