[FEAT] on TAU startup, get historical Twitch data (where possible)

[matthewbrandt]

Is your feature request related to a problem? Please describe.
When TAU is not running, no data is captured in the DB (twitch events table). However, when TAU is started, it doesn't backfill any data that is newly available from Twitch since TAU was shut down. This means the user needs to manually obtain that data via endpoints.

Describe the solution you'd like
On TAU startup, check for endpoints (which provide it) data to be backfilled to close the gap since TAU was last running.

Describe alternatives you've considered
This can be offloaded into an app being developed around TAU, but would be more useful to have embedded in TAU for consistency.

[FiniteSingularity]

I can definitely see the use in this. A few things we will need to figure out-

• What historical twitch events can we retrieve from the Helix API?
• How well does the data from Helix map to the EventSub data?

From an initial glance at the Helix and EventSub docs, it looks like a bit of a mixed bag. A couple of examples:

1. Follows - For follows it looks like there is a 1-to-1 match, and it would be quite simple to implement.
2. Subs - I dont know if it is possible to adequately reconstruct sub events. The Helix data only retrieves who is currently subbed, what their sub tier is, and a small amount of gift sub data. However it does not include any data about when the sub occurred. Therefore we could look at from our past events who should be subbed, and from the current sub-list determine who would have subbed since TAU was last run. HOWEVER, without having a sub date, it makes future iterations difficult, as we will have a sub events that no longer have a sub date. We'll need to think about this one a bit.