Fix: Use fastlane 'adb' action instead of 'sh' command

[nemanjar7]

• Using adb action instead of sh. However, we still have to pass adb_path.
• I added reading the sdk_path from the ENV, to first check for ANDROID_HOME or ANDROID_SDK_ROOT, and only then it defaults to ~/Library/Android/sdk. It will save us some trouble if we end up redoing android-command-line-tools installation, but even if we don't go that way it's still helpful for others.

As an example, I am using all my sdk tools with homebrew (setup where all the tools are in ~/Library/Android/sdk/android-commandlinetools, so I just added $ANDROID_HOME path.

I am passing ENV['ANDROID_HOME'] here, but I assume we can do it in CI/CD as well, so it doesn't have to be in here.

[iBotPeaches]

Have you looked at this file? What I'm nervous about is seeing all these hard-coded paths that we've quickly realized is a bit of a mixed bag between things.

https://github.com/fastlane/fastlane/blob/master/screengrab/lib/screengrab/android_environment.rb

It seems that worked well to find adb - could we follow a similiar pattern if that exists for avdmanager?

I see there is a adb helper you found also and I like that - https://github.com/fastlane/fastlane/blob/master/fastlane/lib/fastlane/helper/adb_helper.rb#L2

Unrelated I wish there was a better nomenclature than "other_action", something like in PHP where you import the class - then call like "adb.adb" or something