Upgrade AGP and Dependencies

[omarismail94]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #2072

Description
Upgrade Android Gradle Plugin from 7.1.1 to 8.1.0 to allow us to update our other dependencies, that rely on having a newer AGP. For example, for the new work manager library to work, it needs to compile on SDK level 33, which the AGP 7.1.1 has not been tested on.

Additionally, we were setting the source compilation to Java 8, but in the AGP that we had, it did not respect that and compiled the source files to whatever the Java version Gradle ran on (usually the default installed on the machine). Our code can't compile to Java 8 as the version of the HAPI FHIR libraries stopped supporting Java 8.

With AGP 8, we have had to make a few changes. First we enforce the usage of Java 11 for compilation. If Java 11 does not exist on the machine, Gradle automatically downloads it. We still support backwards compatibility via desugaring. WIth AGP 8, we are required to have the namespace field in the module-level build script, and not in the AndroidManifest.xml file. This means we can delete a bunch of XML files from our codebase.

Finally, in JaCoCo we disable the need to transform the files for dexing when running instrumentation tests. In each version of AGP after 7.1.1, the API to transform files changed, breaking our instrumentation. However. we do not use JaCoCo for instrumentation when running our CI tool, instead, we use Firebase. Locally, we also do not need JaCoCo to run its transformation when running tests.

Please set the JDK version Gradle uses to Java 17

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)

Screenshots (if applicable)

Checklist

• I have read and acknowledged the Code of conduct.
• I have read the Contributing page.
• I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
• I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
• I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

[jingtang10]

Thanks Omar!