Move release workflow failures to Android Releases

[karlenDimla]

Task/Issue URL: https://app.asana.com/1/137249556945/task/1216513310447906?focus=true
Tech Design URL (if applicable): https://app.asana.com/1/137249556945/project/414730916066338/task/1216144994462267?focus=true

Description

Route GitHub workflow-failure tasks for the four release workflows (create tag, create release task, update release notes, upload to Play Store) into the Releases project instead of the general Android App project.

• Each failure task now lands in the Releases project's blocker section, using the GH_ANDROID_APP_RELEASES_PROJECT_ID and GH_ANDROID_APP_RELEASES_PROJECT_BLOCKER_SECTION_ID repo variables (replacing
  GH_ANDROID_APP_PROJECT_ID / GH_ANDROID_APP_INCOMING_SECTION_ID).

Steps to test this PR

qa-optional

---

Note

Low Risk
CI-only change to Asana routing on workflow failure; no app or release build logic affected, assuming repo vars for the releases project are configured.

Overview
Release GitHub Actions failures now open Asana tasks in the Android Releases project’s blocker section instead of the general Android app project incoming section.

The same asana-project / asana-section swap is applied to the failure-handler step in release_create_tag.yml, release_create_task.yml, release_update_release_notes.yml, and release_upload_play_store.yml. Task names and descriptions are unchanged; only where failures are filed moves to match release-focused triage (consistent with release-blocker vars used elsewhere in CI).

^{Reviewed by Cursor Bugbot for commit a04f4fc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[karlenDimla]

• Move release workflow failures to Android Releases #9209 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[CDRussell]

LGTM, thanks @karlenDimla