Diagnose and recover from Google Play Android Publisher API edit failures: expired, invalidated, or already-in-review edits

Documented steps

1. Start every publishing run with a fresh POST .../applications/{packageName}/edits (edits.insert). Never reuse an editId persisted from a previous CI run.
2. Read AppEdit.expiryTimeSeconds (output-only, seconds since epoch) and treat every operation attempted after that timestamp as invalid.
3. Remember each identity may hold only one open edit per app; calling edits.insert again silently invalidates the prior open edit.
4. Remember that a commit by anyone, or any change made in the Play Console UI, invalidates all other open edits for that app immediately and without notification.
5. Apply modifications (bundles.upload, tracks.update, listings.update) against the current editId. If the edit was invalidated, these calls fail and you must restart from edits.insert.
6. Before committing, GET .../edits/{editId} (edits.get) to confirm the edit still exists, or POST .../edits/{editId}:validate to surface validation errors without publishing.
7. POST .../edits/{editId}:commit to finalize. Committing an invalid edit throws and has no effect, so treat commit failure as a signal to rebuild the whole edit rather than retrying the same id.
8. Set changesInReviewBehavior explicitly. The default, CANCEL_IN_REVIEW_AND_SUBMIT, cancels any review already in flight and submits yours instead.
9. Set changesInReviewBehavior=ERROR_IF_IN_REVIEW to fail fast instead. Expect HTTP 400 with status FAILED_PRECONDITION and ErrorInfo.reason CHANGES_ALREADY_IN_REVIEW, and branch retry logic on that reason string.
10. Treat 5xx as transient and retry with backoff. Treat 409 as a concurrency conflict: re-fetch state or open a new edit rather than blindly retrying.
11. Log packageName, editId and expiryTimeSeconds on every insert so a failed unattended run can be traced to the exact edit window it used.