The failed loading status should not be cached.

## 🐛 Bug Report

There are many reasons for image loading failure, but it is inevitable that the loading will fail due to objective network congestion or busy service. This failure status should not be cached, because when the network recovers, I hope to try loading again, because it has already Once it is cached, it will no longer make actual requests. Only by manually clearing the cache can the actual load be carried out again. However, ordinary users will not think in this direction. Even if they know the reason, they will not know how to clear the cache.

### Expected behavior

Only successfully loaded images should be cached

### Reproduction steps
1. Prepare a picture server and get the URL of one of the pictures.
2. Close the image server
3. Use widgets to load this url
4. Start the image server
5. Then use the widget to load the url

### Configuration

**Version:** 1.x

**Platform:**
- [x] :iphone: iOS
- [x] :robot: Android