Google Payment Client

[sshropshire]

Summary of changes

• Create GooglePaymentClient
• Bump compileSdkVersion and targetSdkVersion to API level 30
• Migrate GooglePayment supplemental classes that originally existed in the braintree-android repo into this repo.

• Breaking Changes

  • Bump minSdkVersion to 21.
  • Remove GooglePayment static client.

  Checklist

  • [x] Added a changelog entry

Authors

• @sarahkoop
• @sshropshire

[sestevens]

Two general thoughts/questions:

1. How does everyone feel about the term GooglePayment that's used on a lot of these class names? It's always seemed slightly weird to me, since the payment method is "Google Pay" not "Google Payment". Would it make sense to change it to GooglePayClient, GooglePayException, etc. or would that conflict with Google's APIs?

2. At one point we talked about moving this library into the main repo, alongside the rest of the payment methods. Would it make sense to do that now? I'd be in favor of having one less repo to worry about.

[sshropshire]

@sestevens Sarah and I agree with both points. Talking it through:

1. How does everyone feel about the term GooglePayment that's used on a lot of these class names? It's always seemed slightly weird to me, since the payment method is "Google Pay" not "Google Payment". Would it make sense to change it to GooglePayClient, GooglePayException, etc. or would that conflict with Google's APIs?

GooglePay is the name of the product and Braintree offers it as a feature of the SDK. Having the names align would be less confusing.

2. At one point we talked about moving this library into the main repo, alongside the rest of the payment methods. Would it make sense to do that now? I'd be in favor of having one less repo to worry about.

This would be awesome. Jumping around the different repos requires some wrangling. We'd be up for both changes if we're cool with the version updating for all modules on deploy, or if we could come up with an alternative to keep each module's semver isolated that'd be cool too.