Bugfix: Change how errors are reported by ImageLoader. Emits as stream instead of re-throwing

[robert-northmind]

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

This is a bug fix

⤵️ What is the current behavior?

If the CachedNetworkImageProvider gets some error when fetching an image url, then internally the ImageLoader will rethrow that error.
This leads to the unwanted behavior that you get an uncaught exception.
And this for example then leads to faulty fatal errors being reported in Crashlytics.

🆕 What is the new behavior (if this is a feature change)?

Instead of throwing the error inside the ImageLoader, we are now emitting the error as a stream error into the current stream.
This has the added benefit that this will not be an uncaught exception.
And all existing ErrorListeners, ErrorBuilders will still work.

💥 Does this PR introduce a breaking change?

No

🐛 Recommendations for testing

You can test this change with the existing example app.
If you run the example app for a mobile device and enabled the debugger to catch uncaught exceptions, then with this fix you will not get any uncaught exceptions. And before this fix, you would get uncaught exceptions for the https://notAvalid.uri and the not a uri at all.

📝 Links to relevant issues/docs

N/A

🤔 Checklist before submitting

• All projects build
• Follows style guide lines (code style guide)
• Relevant documentation was updated
• Rebased onto current develop

Screenshots

These screenshots come from VSCode running the previous version with uncaught exceptions turned on:

And here is a screenshot coming from this version with uncaught exceptions turned on:

[robert-northmind]

I just updated this URL since the old https://blurha.sh/assets/images/img1.jpg didn't point to a resource anymore. You just got back a 404.