Create a stable redis test endpoint so we can run tests in ci

[C-Loftus]

Right now we can't really run tests in ci without spamming upstream rise and also just being very slow; would be much better if we had a stable test redis endpoint so i can just point to that both in ci and local dev

ultimately testing against cached data is not great but there's not a great alternative since it is too slow to request all the queries fresh each time.

[webb-ben]

Realistically a stable redis cache won't do all that much if we are only caching for 24 hours. Can you use mock requests

[C-Loftus]

I think it will help for dev quite a bit since if I am sharing the same cache for local dev and ci then all items will be shared and thus will be quite a bit faster and don't have to wait for items to be refetched each time a pr occurs. It is not perfect, I agree, but I think mocking the API is a bit too verbose since we are dealing with a huge variety of api responses and paginated responses that would be fairly clunky to mock. Also worried about needing to redo all mocks when the upstream inevitably does change something in the future.

I think in terms of TTL I have it currently set to 72 hours. I think that, or even longer, is totally fine since data is very rarely going to change. Most likely scenario is that we get new results that don't affect old urls and results can have a separate ttl in general if we want