Replace check for emulator package with check for sdkmanager

Is your feature request related to a problem? Please describe.

In our case, we only have the emulator package installed for tests and not for the build job. This causes an error “✖WARNING: The Android SDK is not installed or is not configured properly”. CI builds are often run inside containers, and it may not make sense to have an emulator because nested virtualization may not be supported. So now we are made to install the emulator inside a Docker image even though you don’t need an emulator to build an Android binary.

Describe the solution you'd like

It might be more effective to check for the sdkmanager in order to validate whether the Android SDK has been properly installed. The sdkmanager could have the ability to install the emulator if it is missing and required.

Describe alternatives you've considered

Our solution has been to create a workaround in which there is a file that mimics the emulator in order to avoid the error mentioned above.

Anything else?

I hope to contribute to this issue and am actively looking to solve it if approved.

Please accept these terms

• I have searched the existing issues as well as StackOverflow and this has not been posted before
• I agree to follow this project's Code of Conduct

Start by locating the existing Android SDK and emulator validation in the CLI, then identify how sdkmanager is detected or invoked. Done means Android builds no longer require the emulator package, while emulator installation remains available when it is actually needed.