Adding Package Name to Google Play Integration

What does this MR do and why?

This MR adds the Package Name field to the Google Play integration configuration. This additional field serves the purpose to make it possible to validate the configuration has access to the correct app in the Google Play console, as well as adds the configuration variable to the CI pipeline to further simplify the configuration needed in the CI jobs.

Note: This MR also adds an additional Google APIs gem to the Gemfile google-apis-androidpublisher_v3

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

1. Enable the Google Play integration feature flag in the rails console

   Feature.enable(:google_play_integration)

2. Visit the Google Play integration page for a project http://localhost:3001/flightjs/Flight/-/settings/integrations/google_play/edit
3. Only .json file types are allowed. The dropzone will allow any text file with a .json extension, so it fine to create a dummy file locally to test.
4. Adding a dummy Package name like com.gitlab.foo.bar will allow the record to validate and save, but the Test Settings will fail without valid credentials from the Google Play Console.
5. If a allowed filetype is selected the input will change to the name of the file. If a not allowed file is selected, and error message will be displayed.
6. (optional) Testing with a valid Google Play Console account isn't necessary, but if you want to, follow these instructions to set up an account https://developers.google.com/android-publisher/getting_started

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.