[MNT] Rewrite API Parser and Data Loading

[theOehrly]

The API parser and data loading/processing code have reached a point where they should be rewritten from scratch, taking into account what has been learned over the last years. Too many things have been added in to fix problems that have come up. The code flow is convoluted and fragile. The following is a non-exhaustive list of things that need to be done.

Must be done

• rewrite API parser
• remove 150s lap time limit ([BUG] Restart lap times after the red flag #473, [BUG] Duplicate lap times in source data for GRO incorrectly handled in 2020 Round 4 #612, [BUG] Timing data contains laps with incorrect duplicate lap times #404)
• drop usage of Pandas in API parser, switch to all numpy Datetime and Timedelta (Audit all assignments to pd.NaT #728)
• move post-processing code out of Session class

Optional

• allow users to configure what post-processing is done
• drop the F1 Livetiming first approach, make data sources "equal" in importance thereby allowing to load all lap times from Jolpica, for example. Make data source priorities configurable.
• update cache implementation
• enable dynamic data loading (?)

[Casper-Guo]

I may have brought this up before but another useful change will be making use of the TyresNotChanged field in the timing data. This will allow detection of drivers coming into the pit without changing tyres, most commonly seen when the SC comes through the pit. The API treats this event as a new stint even though logically it should be seen as the same stint.

Might be possible to implement this implementation in _fix_tyre_info right now but certainly should be a goal for the new parser

See following traces from 2018 Azerbaijan GP for Ericsson for example:

_api           INFO     {'2': {'TotalLaps': 18}, '3': {'LapTime': '1:59.730', 'LapNumber': 36, 'LapFlags': 0, 'Compound': 'ULTRASOFT', 'New': 'true', 'TyresNotChanged': '0', 'TotalLaps': 0, 'StartLaps': 0}}
_api           INFO     {'3': {'TotalLaps': 1}}
_api           INFO     {'3': {'TotalLaps': 2}}
_api           INFO     {'3': {'TotalLaps': 3}, '4': {'LapTime': '2:28.577', 'LapNumber': 39, 'LapFlags': 0, 'Compound': 'ULTRASOFT', 'New': 'false', 'TyresNotChanged': '1', 'TotalLaps': 3, 'StartLaps': 3}}
_api           INFO     {'4': {'LapTime': '2:16.806', 'LapNumber': 40}}
_api           INFO     {'4': {'TotalLaps': 4}}
_api           INFO     {'4': {'LapTime': '1:55.803', 'LapNumber': 41}}

[theOehrly]

@Casper-Guo I'd be open to fixing this in the current implementation as it is basically a bug. A new parser is not something that'll be done in the next few weeks.

Either implement it in __fix_tyre_data or maybe even in the parser and just drop those messages. After all, no part of FastF1 can do anything useful with them.

[Casper-Guo]

Previously discussed a bit in #717. Just a reminder to close that issue whenever this is fixed