RemoteDataState.Error is rarely handled

Nobody has claimed this yet.

In many parts of the app, we handle data fetching status by setting a relevant part of the redux state to RemoteDataState.NotStarted, then RemoteDataState.Loading and RemoteDataState.Done. If the data fetching errors, we set the relevant state to RemoteDataState.Error.
See `src/shared/components/GetResources.tsx` for an example of this.

The problem is that the component we most often pass this RemoteDataState variable to, (the SpinnerContainer) handles only loading and not started states, and renders children directly if the loading state is Error. in effect we treat Done and Error in the same way, and continue to try to render parts of the app which may depend on the resources we have tried to fetch.

Start with src/shared/components/GetResources.tsx and trace how its RemoteDataState value reaches SpinnerContainer. Inspect SpinnerContainer's handling of NotStarted, Loading, Done, and Error states. Done means fetching errors no longer render dependent children as though loading succeeded, with the relevant behavior covered by tests if the existing component tests are found.

Written by the indexing model from the issue text.