test(ci, android): continued hunt for valid min API for e2e, try 30

continuing to hunt for a viable min/max range of emulator APIs to test

Author: mikehardy

.github/workflows/tests_e2e_android.yml

@@ -33,11 +33,12 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # all APIs below 23, and 27 just do not work
-        # 23-24 appears to work locally but fails in CI
+        # all APIs below 23 just do not work
+        # google-apis doesn't have an emulator for 27
+        # 23-25, 28-29 appears to work locally but fails in CI
         # 26 does not support performance tracing due to hardware acceleration bugs
-        # min-possible + max-possible skew looks like 24 and 34 then
-        api-level: [25, 34]
+        # min-possible + max-possible skew looks like 29 and 34 then
+        api-level: [30, 34]
         arch: [x86_64]
         target: [google_apis]
         # This is useful for benchmarking, do 0, 1, 2, etc (up to 256 max job-per-matrix limit) for averages