As investigated in #4635, there are several github resources that make good candidates for eTag usage in our codebase. By caching those resources in redis and storing their eTag values, our github-facing interface can serve fresh copies of those resources while optimizing for rate-limiting and speed in cases where the resources were not modified since they were last accessed.