DataBindingIdlingResource and Hilt

How can we use `DataBindingIdlingResource` and also use `launchFragmentInHiltContainer`?

`launchFragmentInHiltContainer` is not returning anything. However, I've modified it like this:

```
inline fun launchFragmentInHiltContainer(
fragmentArgs: Bundle? = null,
@StyleRes themeResId: Int = R.style.FragmentScenarioEmptyFragmentActivityTheme,
crossinline action: Fragment.() -> Unit = {}
): ActivityScenario {
val startActivityIntent = Intent.makeMainActivity(
ComponentName(
ApplicationProvider.getApplicationContext(),
HiltTestActivity::class.java
)
).putExtra(
"androidx.fragment.app.testing.FragmentScenario.EmptyFragmentActivity.THEME_EXTRAS_BUNDLE_KEY",
themeResId
)

ActivityScenario.launch(startActivityIntent).onActivity { activity ->
val fragment: Fragment = activity.supportFragmentManager.fragmentFactory.instantiate(
Preconditions.checkNotNull(T::class.java.classLoader),
T::class.java.name
)
fragment.arguments = fragmentArgs
activity.supportFragmentManager
.beginTransaction()
.add(android.R.id.content, fragment, "")
.commitNow()

fragment.action()
}.also {
return it
}
}
```
Is this a good approach?

Start by reviewing the shown launchFragmentInHiltContainer helper and how DataBindingIdlingResource is used in the Android architecture samples. Determine whether the helper should return an ActivityScenario and support the idling resource, then verify the proposed approach against the existing sample tests; done means the intended combination is documented or the helper behavior is corrected.

Written by the indexing model from the issue text.