Automation/9887-chanel-improve-monitoring-when-release-does-not-release

Description of Change

The Android 2.37 and 2.38 releases never released - we need to figure out why, and fix what went wrong so it doesn't happen again. Investigate if we can better detect and alert when a release doesn't release

Initial notes

the play store flagged/rejected a build of ours as not meeting their data policy on September 16. we thought that rejection was on a test build, and that everything for production builds was OK our automated slack messages kept saying everything was released (example) On October 14, trying to follow up on if LinkWithAnalytics crash was happening in the latest Android version, we saw that firebase was showing 2.36 as the latest released version for Android On October 15, digging in further, we realized that 2.37 and 2.38 had never been released. It appeared that after rejecting a build, we needed to manually press a button in the google play console, in order for the play store review team to start reviewing our app again, post-rejection ("send 7 changes for review" blue button in screenshot) Pressed that button, google play approved within ~30 min, and we released 2.38 to the play store on Oct 15 at 1:37pm central time.

Screenshots/Video

Testing

[ ] Tested on iOS
[ ] Tested on Android

Reviewer Validations

PR Checklist

Reviewer: Confirm the items below as you review

[ ] PR is connected to issue(s)
[ ] Tests are included to cover this change (when possible)
[ ] No magic strings (All string unions follow the Union -> Constant type pattern)
[ ] No secrets or API keys are checked in
[ ] All imports are absolute (no relative imports)
[ ] New functions and Redux work have proper TSDoc annotations

For QA

Run a build for this branch

department-of-veterans-affairs / va-mobile-app