Publish a new Android App Bundle to a Google Play track using the full edits.insert to bundles.upload to tracks.update to commit lifecycle

Documented steps

1. POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/{packageName}/edits (edits.insert) with an empty body. Capture AppEdit.id as editId and note expiryTimeSeconds.
2. Upload the .aab to the SEPARATE media-upload base path, which is prefixed with /upload/: POST https://androidpublisher.googleapis.com/upload/androidpublisher/v3/applications/{packageName}/edits/{editId}/bundles?uploadType=media
3. Example: curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/octet-stream" --data-binary @app.aab "https://androidpublisher.googleapis.com/upload/androidpublisher/v3/applications/$PKG/edits/$EDIT_ID/bundles?uploadType=media"
4. Read versionCode from the returned Bundle resource; that integer is what you reference in the track release, not the version name.
5. GET .../edits/{editId}/tracks/{track} (edits.tracks.get) first so you know which existing releases and versionCodes are already on the target track.
6. PUT .../edits/{editId}/tracks/{track} (edits.tracks.update) with a Track body: {"track":"production","releases":[{"versionCodes":["<uploaded versionCode>"],"status":"completed","releaseNotes":[{"language":"en-US","text":"What's new"}]}]}
7. Use the real API track identifiers: production is 'production', open testing is 'beta', internal testing is 'qa'. Closed testing tracks use the custom name you created.
8. Optionally POST .../edits/{editId}:validate (edits.validate, empty body) to check the edit is publishable without committing it.
9. POST .../edits/{editId}:commit (edits.commit, empty body) to publish. Set changesInReviewBehavior and changesNotSentForReview deliberately rather than relying on defaults.
10. Inspect the commit response for errors. Commit success means the edit was accepted, not that the release is live to users.