e2e migration test on PR targeting master

[lydavid]

• gco master
• install app
• maestro click through all screens¹
• gco release branch
• install app again
• maestro click through all screens again

This is all based on the assumption that between GHA steps, we maintain the same AVD. Otherwise, each time we install our app, it will be a fresh install, which will not let us test that a migration from the master branch to the release branch worked without crashing.
Confirmed with https://scans.gradle.com/s/6ulorrahmvalo/timeline and https://scans.gradle.com/s/asm2laxnfiir2/timeline

Continuation:

• expand release e2e testing while keeping commit e2e smaller #1168

Footnotes

1. Because we run maestro test with $HOME/.maestro/bin/maestro test .maestro, the test suite will need to exist already on master. ↩

[lydavid]

Not able to see the evidence of previous run in https://github.com/lydavid/MusicSearch/actions/runs/9726640692

• retry with maestro