chore: sync actions from gh-aw@v0.79.5

[github-actions]

Automated sync of actions from gh-aw at v0.79.5.

[Copilot]

Pull request overview

Automated sync of the gh-aw action scripts to v0.79.5, updating several setup-time utilities around secret validation, safe-outputs tooling, OTLP span attributes, and sample replay logic.

Changes:

• Add Copilot org-billing aware handling to Copilot token validation and improve branch detection in detached-HEAD scenarios.
• Tighten/adjust safe-outputs behavior for push_to_pull_request_branch and improve related patch/branch derivation in sample replay.
• Ensure OTLP gh-aw.aic is emitted as a numeric attribute (defaulting to 0) when token-usage-owning jobs have no data.

Show a summary per file

File	Description
setup/js/validate_secrets.cjs	Adds Copilot org-billing skip logic for Copilot token checks.
setup/js/send_otlp_span.cjs	Ensures gh-aw.aic numeric attribute defaults to 0 when appropriate.
setup/js/safe_outputs_tools.json	Updates tool schema for push_to_pull_request_branch (notably around branch handling).
setup/js/safe_outputs_handlers.cjs	Derives push_to_pull_request_branch source branch from the current checkout and improves errors.
setup/js/get_current_branch.cjs	Improves handling of detached-HEAD by falling back to GitHub env refs.
setup/js/comment_memory.cjs	Skips comment-memory upsert when there’s no triggering context.
setup/js/apply_samples.cjs	Adds PR head-ref derivation + per-repo token selection; makes pre-staging async.
setup/js/add_comment.cjs	Expands allowed target values and warns (instead of failing) on unknown targets.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

setup/js/safe_outputs_tools.json:963

• push_to_pull_request_branch uses a strict schema (additionalProperties: false) and the MCP core rejects unknown parameters before the handler runs. Removing the branch property means older clients that still send branch will now hard-fail validation, even though the handler attempts to defensively strip it. If backwards compatibility is intended, keep accepting branch in the schema (but document/ignore it).

      "properties": {
        "message": {
          "type": "string",
          "description": "Commit message describing the changes. Follow repository commit message conventions (e.g., conventional commits). This field is named message, NOT commit_message.",
          "x-synonyms": ["commit_message"]

• Files reviewed: 8/8 changed files
• Comments generated: 1