give reasons why a reader fails is_supported_image

[toloudis]

Feature Description

is_supported_image returns True or False when testing a reader to see if it "can load" the given image. When it returns False, this may sometimes indicate an error but it happens silently and users never know without debugging.
Many times there might be an exception being caught internally or extended error information which could be propagated up to the loop over all readers.

Use Case

see discussion in https://github.com/bioio-devs/bioio-bioformats/issues/21

Solution

Consider returning extended error information along with the boolean from is_supported_image, or allow is_supported_image to raise exceptions that can be caught in bioio, so it can print error info. Bear in mind that we prefer is_supported_image to be as computationally cheap as possible in case we have to loop through many readers.

Alternatives

[toloudis]

I was missing some key info, that we actually already do catch exceptions from is_supported_image, so perhaps the "solution" here is to document that readers should let exceptions be raised from their own is_supported_image implementations. (see the linked issue above)