[Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli)

Umbrella tracking issue for all open upstream dependency release-note action items.

Each sub-issue was auto-generated by the `deps-release-notes` agentic workflow and summarizes what ado-aw should do in response to a new release of a key upstream dependency:

- **awf** — Azure Workflows Firewall / network-isolation binary
- **mcpg** — MCP Gateway
- **copilot-cli** — GitHub Copilot CLI

The 18 most-recent open issues are linked as sub-issues. An additional 16 older issues share the same theme and may be added as sub-issues in a follow-up: #990, #983, #970, #951, #950, #931, #930, #903, #902, #882, #881, #880, #859, #851, #843, #803.

Closing this parent when all sub-issues are resolved (or explicitly deferred) gives a single point of visibility into the dependency-health backlog.

> Generated by [Issue Arborist](https://github.com/githubnext/ado-aw/actions/runs/28530704230) · 110.7 AIC · ⌖ 10.6 AIC · ⊞ 6K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fado-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fado-aw%2Fissue-arborist%22&type=issues)

Start by reviewing the 18 linked sub-issues for the specific release-note actions and compare them with the older issues listed in the parent. This issue is done when all sub-issues are resolved or explicitly deferred and the dependency-health backlog is accounted for.

Written by the indexing model from the issue text.