Livescores (v2) orphan data handle

[migbash]

Related/parent => #1108

DESCRIPTION

Multi-part issue for Livescores-v2 widget.

1. Orphan Issue
2. Firebase | Outdated Data - 🔥 Hot Fix - Firebase - live Updates issues #1108
3. Firebase | Connection lost / freeze -> 🔥 Hot Fix - Firebase - live Updates issues #1108

---

1. ✅ IMPLEMENTED

At times, the platform reloads as per a feature by the Realtime DB from Firebase, when a connection is lost, this loads the correct, and most up-to-date data for the livescroes-v2 widget. However, when this does not happen (or doesn't need to), the user is stuck relying on the livescores_now_scoreboard data to keep getting the latests new data. But, after 30 or X minutes of inactivity, the fixture might have finished and removed from the livescores_now_scoreboard data. This causes an orphan data to get stuck with a LIVE status (or otherwise incorrect data). As data is no longer avaialble on the livescores_now_scoreboard - a request needs to be made to the source Hasura to get the latest orphan data, for the target orphan fixtures.

For example:

Ended game

Same game (above) but mobile is off - example of orphan

DATA IS STILL FLOWING CORRECLTY ACCORDING TO LOGS:

• Issue is regarding the NON-UPDATING of data, despite no errors and data still flowing in by the (document.hidden) validation check;

⚠️ HOWEVER, NOTE that the "real-time" no longer flows-in/works in this case…