Split non-caching functionality out of fetchWithCache, and utilize in appropriate cases

`fetchWithCache` has both functionality explicitly related to caching a request, and functionality that just supports good practices and simplifications of fetch calls. In cases where one wants to make use of latter, but not the former, responses will be cached unecessarily. We should move the non-cache relate functionality of fetchWithCache into another function, and then make use of that function in any such existing cases.

Start by locating fetchWithCache and reviewing its callers to distinguish caching uses from cases that only need its non-caching behavior. Done means the shared non-caching functionality has its own function and appropriate existing callers use it without unnecessarily caching responses.

Written by the indexing model from the issue text.