* Adjust DispatcherProvider interface to return type `CoroutineContext`.
This is a preamble to fix a few coroutine tests that require time advancement.
We need to be able to pass the TestCoroutineScope's context to classes under test.
This can now be done using CoroutineContext.asDispatcherProvider().

* Fix compile error in test

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>
Co-authored-by: ralfgehrer <mail@ralfgehrer.com>

* Add tooling layout tag for better overview

* Ignore error for ProtectedPermissions

* Add instrumentation tests to capture screenshots in Onboarding flow

* Specify java version to avoid assembling APK failure

* Define custom annotation for tests

* Use fastlane Screengrab

* ignore screenshots folder

* Remove redundant imports and rules

* Add View assertion to make sure Fragment is already displaying its views to avoid capturing blank screenshots

* List some configurations for fastlane

* Add TODO for locale change

* Allow timestamp suffix to have different screenshots names

* Scroll and grab another screenshot in OnboardingFragment

* Delete import

* Filter tests using Screenshot annotation

* Add locale change rule in UI tests

* Limit screenshots only for DE locale

* Enable screenshots for all locales

* Enable screenshot test

* lint cleaning

* Use JavaVersion to specify java version

* Add an inline function that defaults to AppTheme

* Update dcos for launchFragmentInContainer2

* lint

* Define generic apk_path

* Support cleaning device status bar before taking screenshot

* Correct docs

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

* Change primary key for risk result database to a monotonic ID.
This prevents time travel from breaking "get latest" as we will get the latest by monotonic ID, instead of "calculatedAt".

* We don't need `fallbackToDestructiveMigrationFrom(3)` until we actually upgrade the schema to 3.

* Fix database test (missing monotonicId)

* Catch exceptions during migrations and recreate the table.

* Add check for result size after recreating+insertion.

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

Introduce VM injection for home screen and enable screen testing (EXPOSUREAPP-2946, EXPOSUREAPP-2948) (#1320)

* Rename "MainFragment" to "HomeFragment"
Add VM injection.
Move initial logic into VM.

TODO: Move more code, write more tests.

* Additional refactoring, moving logic out of the Fragment.
Moving code into their own encapsulated routines/components.
Use composition to reuse TracingViewModel, SettingsViewModel and SubmissionViewModel

* Introduce @AppContext annotation to prevent anyone mistaking it for something else.

* Add VM to RiskDetailsFragment

* Simplify nested viewmodels, here: TracingViewModel.kt

* Add skeletons instrumentation test skeleton for single fragments with injection and mocking.

* Address PR comments.

* Introduce sealed events class, + some refactoring.

* Make the linter happy.