Add smoke test for Android glue code

[jamilbk]

Similar to #4287, we do have the ability to launch a full Android simulator in CI.

The goal of this issue is to hit the Session.connect codepath for Android in order to catch basic runtime errors.

The MVP of this would likely involve:

• Building a client in CI (we already do this)
• Launching the simulator, avd
• Installing the app package into the simulator
• Launching it with in stub mode (no portal, service account token, etc)
• Check for success somehow (ping the TUN device, check if tun0 or tun1 exist, etc)

[thomaseizinger]

• Launching the simulator, avd

• Installing the app package into the simulator

• Launching it with in stub mode (no portal, service account token, etc)

It would be amazing to somehow pack this into a docker container so we can just add it to the docker compose setup and just open a web browser with httpbin or something on it. That would even smoke-test DNS and catch things like these runtime errors. Maybe stuff like https://github.com/budtmo/docker-android could be used? (Disclaimer: Never used it.)