Add a happy path E2E test for Android

[opatry]

There were several times bug easily avoidable with this kind of test.
Typically the use of navigation keys and LazyColumn items keys is sometimes fragile on Android (compared to desktop), it requires keys to storable in a Bundle which is easy to miss.

• Setup E2E tests (see Programmatic store screenshot generation #210 for bootstrap)
• Skip onboarding
• Create a task list
• Create a list
• Complete the task
• Expand the "completed task" section and check the task is here
• Restore the completed task
• Delete the task
• Rely on string resources from :tasks-app-shared instead of test tags when possible
• Run on emulator in CI (if not, the effort is kinda pointless)
  • Would Firebase test lab be a good fit?
    • https://firebase.google.com/docs/test-lab/android/get-started
    • https://medium.com/@peterkagure/running-instrumented-tests-on-github-actions-with-firebase-test-lab-ac17bb36ae9c
  • Alternative would be to use an action to setup emulator (or do it on our own…)
    • https://github.com/marketplace/actions/android-emulator-runner
    • https://dev.to/ychescale9/running-android-emulators-on-ci-from-bitrise-io-to-github-actions-3j76
    • https://www.atkinsondev.com/post/android-emulator-tests-github-actions/
•  Reduce emulator setup time leveraging AVD snapshots
  • https://github.com/ReactiveCircus/android-emulator-runner?tab=readme-ov-file#usage--examples
• Take a screenshot on failure and provide it in CI results ideally (at least, would allow debugging locally more easily?)
  • does Firebase test lab provide this for free?
• Better control step time… despite emulator setup caching, it takes around 6m-7m vs 3m for the whole build… 2x build time for a 3sec UI tests, a bit sad.
  • Made a nightly Job to mitigate this
• Make the E2E workflow a daily/nightly one and only trigger it if there were changes since last run.