Fix android image loading race condition and improve logging

[albyrock87]

Description of Change

This PR aims to solve three issues:

1. Switching between Shell Tabs destroys the Fragment causing unwanted image unloading:
   Reloading images upon re-attach was handled in Check to see if Image Should Reload When Attached #24023 but we can provide a better UX here and avoid flashes while going back to the initial tab.
2. Random flashes while scrolling collection view caused by a race condition in image loading:
   Glide is race-condition free, but we were setting the Drawable asynchronously in the next loop, this may generate glitches under some scrolling condition in collection view
3. It's really hard to debug our beloved Glide integration:
   I've added proper logging mechanics which can be enabled via adb before running the application:

   adb shell setprop log.tag.Glide VERBOSE
   adb shell setprop log.tag.MauiCustomTarget VERBOSE
   adb shell setprop log.tag.MauiCustomViewTarget VERBOSE
   

   Example logs:

   D Glide   : Finished loading BitmapDrawable from MEMORY_CACHE for FontModel{color=#FF000000, glyph='f111', textSize=84.0, typeface=android.graphics.Typeface@898fd220} with size [-2147483648x-2147483648] in 0.202625 ms
   V MauiCustomViewTarget: onResourceReady: FontModel{color=#FF000000, glyph='f111', textSize=84.0, typeface=android.graphics.Typeface@898fd220}
   

Issues Fixed

#14587
#25783

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).