Temporarily remove instrumented test(s).

The project's instrumented tests consist of a single test which sets a
SharedPreference, then verified that the SharedPreference was set.

I humbly submit that this is not worth the trouble of having the CI
server download the system image, spin up an emulator, load the APK, and
run it just for this purpose.

Once the instrumented tests are ready for prime time, we can reinstate
instrumented tests in CI.

Author: dbrant

.travis.yml

@@ -20,15 +20,10 @@ android:
   - extra-android-m2repository
   - android-22
   - android-28
-  - sys-img-${ANDROID_ABI}-${ANDROID_TARGET}
   licenses:
   - android-sdk-license-.+
-before_script:
-- echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI
-- emulator -avd test -no-audio -no-window -no-boot-anim &
-- android-wait-for-emulator
 script:
-- "./gradlew -Pcoverage clean check connectedCheck jacocoTestReport"
+- "./gradlew -Pcoverage clean check jacocoTestReport"
 - if [ "$TRAVIS_PULL_REQUEST" == "false" ] && [ "$TRAVIS_BRANCH" == "master" ]; then
   mkdir -p app/src/prodRelease/play/release-notes/en-US;
   fi