Revert fast initialization of Coil

As discussed in coil-kt/coil#2097 the problem is caused by regitering system services, which will be fixed in 2.6.0

Change-Id: I9085309780508137f10b25ff82deed3c62e5d159

Author: mlykotom

app/src/main/java/com/google/samples/apps/nowinandroid/util/ImageLoaderAsyncFactory.kt

@@ -17,9 +17,9 @@
 package com.google.samples.apps.nowinandroid
 
 import android.app.Application
-import coil.Coil
+import coil.ImageLoader
+import coil.ImageLoaderFactory
 import com.google.samples.apps.nowinandroid.sync.initializers.Sync
-import com.google.samples.apps.nowinandroid.util.ImageLoaderAsyncFactory
 import com.google.samples.apps.nowinandroid.util.ProfileVerifierLogger
 import dagger.hilt.android.HiltAndroidApp
 import javax.inject.Inject
@@ -28,9 +28,9 @@ import javax.inject.Inject
  * [Application] class for NiA
  */
 @HiltAndroidApp
-class NiaApplication : Application() {
+class NiaApplication : Application(), ImageLoaderFactory {
     @Inject
-    lateinit var imageLoaderAsyncFactory: ImageLoaderAsyncFactory
+    lateinit var imageLoader: dagger.Lazy<ImageLoader>
 
     @Inject
     lateinit var profileVerifierLogger: ProfileVerifierLogger
@@ -40,7 +40,7 @@ class NiaApplication : Application() {
         // Initialize Sync; the system responsible for keeping data in the app up to date.
         Sync.initialize(context = this)
         profileVerifierLogger()
-        // We set immediately Coil's image loader factory to prevent initialization with the first image.
-        Coil.setImageLoader(imageLoaderAsyncFactory)
     }
+
+    override fun newImageLoader(): ImageLoader = imageLoader.get()
 }