✅ Isolate test by using mocked dependency rule to tear down state

By setting the dependency provider to null, all async tasks are still
live. And newly created dependencies are no more managed by the mocked
dependency rule. So new async tasks are not waited properly at the end
of the test.

This means that the test was previously still living while other tests
were executed.

By using the rule to tear down the in memory state, then all async tasks
are waited on properly and all new dependencies are still managed and
injected by the rule.

publisher-sdk/src/androidTest/java/com/criteo/publisher/integration/IntegrationRegistryTest.kt

@@ -18,8 +18,6 @@ package com.criteo.publisher.integration
 
 import android.content.SharedPreferences
 import com.criteo.publisher.CriteoUtil.givenInitializedCriteo
-import com.criteo.publisher.DependencyProvider
-import com.criteo.publisher.MockableDependencyProvider
 import com.criteo.publisher.mock.MockedDependenciesRule
 import com.criteo.publisher.mock.SpyBean
 import com.criteo.publisher.util.BuildConfigWrapper
@@ -91,9 +89,8 @@ class IntegrationRegistryTest {
   fun integration_GivenPreviouslyDeclaredOneAndNewSession_ReturnDeclaredOne() {
     integrationRegistry.declare(Integration.IN_HOUSE)
 
-    MockableDependencyProvider.setInstance(null)
+    mockedDependenciesRule.resetAllDependencies()
     givenInitializedCriteo()
-    integrationRegistry = DependencyProvider.getInstance().provideIntegrationRegistry()
 
     val integration = integrationRegistry.readIntegration()