Fallback Tracks posted to Playlog without proper start time assigned

Fallback Tracks are not posted to the playlog properly. A default datetime of 1970-01-01T01:00:00 is always used leading to an unique key constraint error on the API backend:

engine-api-postgres-1  | 2025-05-30 15:30:21.116 CEST [66] ERROR:  duplicate key value violates unique constraint "playlog_pkey"
engine-api-postgres-1  | 2025-05-30 15:30:21.116 CEST [66] DETAIL:  Key (track_start)=(1970-01-01 01:00:00) already exists.
engine-api-postgres-1  | 2025-05-30 15:30:21.116 CEST [66] STATEMENT:  INSERT INTO playlog (track_start, track_artist, track_album, track_title, track_duration, track_type, track_num, playlist_id, timeslot_id, show_id, show_name, log_source, is_synced) VALUES ('1970-01-01T01:00:00'::timestamp, '', '', '', 5836.0, 0, 1, NULL, '-1',  -1, 'Fallback', 1, false)
engine-api             | 2025-05-30 15:30:21,117:engine-api:INFO - Playlog for '1970-01-01 01:00:00' is already existing in local database. Skipping... - [service.py:179-store_playlog()]