The launcher name on Android 11 is returned as com.android.settings instead of the actual launcher package name

`getLauncherPackagename()` returns `com.android.settings`. So `mDevice.wait(Until.hasObject(By.pkg(launcherPackage).depth(0)), LAUNCH_TIMEOUT);` doesn't really wait for the launcher package.
I believe this is due to the package visibility changes on Android 11.

Our test setup consisted of this check before starting with the tests:
`String currentPackageName = device.getCurrentPackageName();
if (currentPackageName != null) {
assertEquals(packageName, currentPackageName);
}`

This failed as currentPackageName returned as `com.google.android.apps.nexuslauncher` and getLauncherPackagename() returned `com.android.settings`.

Comienza rastreando getLauncherPackagename() y la llamada mDevice.wait(Until.hasObject(By.pkg(launcherPackage).depth(0)), LAUNCH_TIMEOUT); después, reproduce la comprobación de configuración usando device.getCurrentPackageName() en Android 11. Se considera completado cuando el paquete del launcher se identifica como el launcher real en lugar de com.android.settings y la espera apunta a ese paquete.

Escrito por el modelo de indexación a partir del texto del issue.