Handle large GitHub releases (use caching!?)

For OpenGApps I would like to include a badge with # downloads of our releases.
But already even one single release of one architecture often gives timeouts, like: [](http://opengapps.org/arch=arm)

While I would prefer to even do:
[](http://opengapps.org/arch=arm)

And I would like to do that for our other architectures (arm64,x86,x86_64) preferably even with a grand-total for all of the 4 repositories together.
We do daily releases, so we are the "weird" one and not the typical use-case, but I would really like to use the badges.

Some caching of non real-time data would not hurt the use-case, since we are well above 3 million downloads...

(see currently regularly failing implementation at https://github.com/opengapps/opengapps/blob/master/README.md )

Start with the failing badge implementation linked from the OpenGApps README and trace how GitHub release download counts are currently fetched. Determine how large and combined release totals should be cached, then verify that the affected badges render reliably for the listed architectures and repositories without repeated timeouts.

Written by the indexing model from the issue text.