Investigate necessity for guava `x.x.x-android` vs `x.x.x-jre`

[diegomarquezp]

Our guava version is as follows:

google-auth-library-java/pom.xml

Line 79 in e7d4380

<project.guava.version>33.4.0-android</project.guava.version>

However, sdk-platform-java declares the x.x.x-jre version.

Investigate the need for this discrepancy.

[lqiu96]

New data points from discussion with @zhumin8:
Apiary Runtime declares support for Android 1.6+: https://github.com/googleapis/google-api-java-client?tab=readme-ov-file#supported-java-environments

Apiary clients can use Google Auth Library and we may need to support that use case.

From Min:

Sounds like the main difference of these two flavors is that -android supports Java 7. The JRE flavor is a superset of the Android flavor. See https://github.com/google/guava/wiki/ReleasePolicy#flavors

GAPICs using shared-deps pull in guava-jre. If we opt that GAPICs promise no compatibility on Android, then shared-deps can continue to use -jre and auth supports -android.

If we merge the repos together only want to manage one flavor of guava (-jre vs -android), then may need to choose -android for maximum support across ALL client library types.