[Feature] Cache commit activity info / More often reloads

[JeJutic]

Feature Description

I would suggest adding cache of the activity info so that when user is offline, they still can see previously fetched info about activity. I guess, it can be implemented with a local file containing json map of date and activity on this date. Cons: maintaining an extra file, hence possibility of IO bugs.

Or extension could try reloading the info more often if the previous attempt failed due to a network error. This way the user will get commit info quite soon after turning on the internet. Cons: if requests were actually sent and user just didn't receive acknowledgments, they can unintentionally DDoS github API.

Why is this needed?

I don't have internet always turned on so most of the time I see "No commit data available". And when I turn it on for some time, refresh timings usually miss it.

[funinkina]

Interesting ideas.

1. A cache will be a good idea in this case to address the no internet connection issue. This will also solve "No commit data available" on startup as we can just read the cache from last boot.
2. Fetching the info more often is not an ideal solution in my opinion, we can try exponential backoff to avoid getting rate limited from github's API.
3. If you want immediate updates when commited/pushed, we can create a git hook that forces the extension to update the info.