Increase robustness when scanning for content

[Abestanis]

Suggestion

To prevent issues like #122, we should:

• Be more robust and don't fail the entire content search because one item fails. We should catch exceptions on an item level and ignore them.
• Catch errors in the content search and show an error UI instead of hanging forever.
• Handle more fields being null. It looks like all columns in the Android media database can be null, based on the create statement here and the fact that the album database is just a view into the files database, so we should be more resilient against nulls.

[Abestanis]

Also, off topic, shouldn't we undraft https://github.com/nt4f04uNd/sweyer/releases/tag/untagged-88d5c1dd963c02bce466 ?

[nt4f04uNd]

Also, off topic, shouldn't we undraft https://github.com/nt4f04uNd/sweyer/releases/tag/untagged-88d5c1dd963c02bce466 ?

True

[nt4f04uNd]

Your suggestions seem reasonable

[nt4f04uNd]

It looks like all columns in the Android media database can be null

This is crazy to me, by the way