[Parent] Safe-output executor E2E test coverage and tool correctness

Tracks open issues concerning the correctness, completeness, and E2E test coverage of safe-output tools in the `executor-e2e` harness and the safe-output Rust implementations.

## Open issues

- #aw_soexec sub-issues cover:
- **E2E test harness gaps**: safe-output actions that are never exercised by the `executor-e2e` definition, causing silent regressions.
- **Implementation bugs**: missing file staging, access-control failures, and missing NDJSON fields that prevent tools from executing successfully in Stage 3.
- **Tool capability gaps**: safe-output tools lacking features (e.g. inline suggestion rendering) needed by agents.

## Related issues (tracked here)

- #1422 — `queue-build` never smoke-tested: `E2E_QUEUE_PIPELINE_ID` unset in executor-e2e definition
- #1421 — `upload-build-attachment` & `upload-pipeline-artifact` never exercised: harness emits un-staged NDJSON (missing `staged_file`)
- #1103 — `add-pr-comment`: render inline threads as applyable single/multi-line suggestions
- #381 — `fix(safe-outputs)`: add file staging to `upload-workitem-attachment`
- #471 — `upload-pipeline-artifact` fails with `ContainerWriteAccessDeniedException` when uploading to other builds

> Generated by [Issue Arborist](https://github.com/githubnext/ado-aw/actions/runs/28974453344) · 56.3 AIC · ⌖ 8.57 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 reading the executor-e2e definition and the linked issues #1422, #1421, #1103, #381, and #471. Determine which safe-output actions and Rust implementations remain affected; done means the listed harness gaps, staging or access failures, missing fields, and capability gaps are addressed and the relevant actions execute successfully in Stage 3.

Written by the indexing model from the issue text.