[ci] add retries for test-suite android-test (#22298)

# Why

android emulator on github actions is occasionally flaky.

# How

retry three times for the use-android-emulator action. the main

[ci] add retries for test-suite android-test (#22298)

# Why

android emulator on github actions is occasionally flaky.

# How

retry three times for the use-android-emulator action. the main idea is `continue-on-error: true` and `if: steps.retries-n.outcome == 'failure'`

# Test Plan

ci passed (though i does not get a chance to repro the flaky emulator. let's ship it and see)

show more ...

[ci] avd api 33 (#22216)

# Why

our `targetSdkVersion` is now 33, we should update the emulator for 33 as well.

# How

- update api to 33
- introduce `use-android-emulator` action and remove

[ci] avd api 33 (#22216)

# Why

our `targetSdkVersion` is now 33, we should update the emulator for 33 as well.

# How

- update api to 33
- introduce `use-android-emulator` action and remove the emulator from expo-caches action. that would put all emulator settings in a single place. other than that, i noticed that emulator booting from snapshot is not quite stable. it just reduces about two minutes and waste cache disk size. this pr also removes the emulator cache.
- based on #22214, we can now build apks on ubuntu runners and then run tests on macos runner. that would save the macos runner limit a little bit.

> **Note**
google only provides api-33 emulator image with google_apis target and [it's not very stable](https://github.com/ReactiveCircus/android-emulator-runner/discussions/286#discussioncomment-4028889). it sometimes has the SystemUI ANR. i've tried as much as i can to supress the SystemUI ANR error. if the error rate is too high, i will disable the slack notification for test-suite android-test failures.

# Test Plan

- ci passed
- android instrumentation test is also broken on main. will follow up in a separated pr.

show more ...