Revert "Respect and pass through ANDROID_USER_HOME and ANDROID_AVD_HOME"

[rmartin16]

Changes

• Reverts Respect and pass through ANDROID_USER_HOME and ANDROID_AVD_HOME #1673
• Closes avdmanager is not compatible with AVDs created by other instances of Android SDK or AVDs created by newer instances of Android SDK #1688
• Reopens Cannot support non-standard location for .android directory #1665

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[rmartin16]

PyGObject 3.48.0 was released 2 hours ago and is failing to build/install on Fedora 39 with Python 3.12.

potentially related: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/488

[rmartin16]

While that PyGObject issue says "installing python3-setuptools" should resolve the issue, I think it only resolves it for users not using build isolation. When I add setuptools to build-system.requires in PyGObject's pyproject.toml, only then can I build it on Fedora 39.

[rmartin16]

Logged at https://gitlab.gnome.org/GNOME/pygobject/-/issues/622.

[rmartin16]

Confirmed fix in https://gitlab.gnome.org/GNOME/pygobject/-/merge_requests/302 addresses this issue.

They mentioned pushing out a new release for this....so, CI will pass once that release is out.

[rmartin16]

And resolved with PyGObject==3.48.1 release.

[rmartin16]

And now Flatpak builds are failing on PyGObject....have to look at that later...

[edit] Resolved Flatpak build issues in beeware/briefcase-linux-flatpak-template#37

[freakboy3742]

Heh - looks like that my "do we want to have briefcase use it's own AVD HOME" comment on the original PR turned out to be prophetic...

[rmartin16]

Heh - looks like that my "do we want to have briefcase use it's own AVD HOME" comment on the original PR turned out to be prophetic...

haha....well, not its own per se....just the same one that Android Studio would be using

Nonetheless, this means I definitely won't be able to run the emulator on that other device....although, my next limitation was RAM usage, soooo.... (and I only really cared about that since its the device I'm bringing to pycon). Running one remotely and windowless should still work fine.