cache network status check after live

Currently the data endpoints check the indexer sync status before serving requests.

This hits the db on every request. Once the stage is LIVE, we dont expect it to go down quickly, so we could cache the LIVE state and refresh it every 5-10 seconds instead of checking for every request.

There should be proper performance/load testing before doing this, to make sure the network status check does not impact data endpoint performance

Start by locating the data endpoints' indexer sync status check and the database query it performs. Add performance/load tests comparing the current behavior with a cached LIVE state refreshed every 5–10 seconds; done means LIVE avoids a database check on every request without harming endpoint performance.

Written by the indexing model from the issue text.