It may make sense to capture fetch errors that are otherwise "dropped on the floor" and show it as a toast error message (with ability to find more details). 

This should only be done if we know all places that errors are dropped are actual bugs. If there are cases where dropped errors on fetch (eg 404) are normal cases (ie no test results when opening test tab) then that should be fixed as part of the scope of this. 

In scope: 

• Allow consumers of fetch to opt out of errors for cases like 40x (so they aren't logged, or displayed)
• Allow showing of error to the user 

cc jamesdumay do you still think this is a good idea?