Reduce noise from agentic workflow failure reports #10120

Agentic workflows currently create tracking issues for several transient or expected conditions. This produces noisy issues that do not require maintainer action and can duplicate the more useful categorized failure report.

The workflows should:

• keep actionable agent, configuration, and code-push failures visible
• keep transient runtime failures and empty agent runs in workflow logs instead of opening issues
• suppress expected missing-data reports from the best-effort extension PR labeler
• disable duplicate failed-job reporting
• require an explicit safe output when an agent completes without making a change
• keep Issue Triage missing-data failures visible so metadata-access regressions remain actionable
• batch extension labels within the runtime limit

Regenerate the compiled workflows with the current gh-aw version after updating the workflow sources.