Fix intermittent Kiro/Cursor auth by updating Kiro egress allow-list and SECRET_* API key fallback

[Copilot]

Intermittent auth failures in Kiro/Cursor smoke runs were tied to two gaps: Kiro traffic to required AWS endpoints was still denied by firewall defaults, and harness scripts did not read the SECRET_* API key names used by the AWF entrypoint env sanitization.

• Kiro network allow-list update

  • Added missing domains to Kiro network.defaults:
    • q.us-east-1.amazonaws.com
    • client-telemetry.us-east-1.amazonaws.com

• Auth harness env fallback

  • Updated harness auth key resolution to support both original and entrypoint-renamed env vars:
    • Kiro: KIRO_API_KEY → fallback to SECRET_KIRO_API_KEY
    • Cursor: CURSOR_API_KEY → fallback to SECRET_CURSOR_API_KEY

• Compiled workflow artifacts

  • Recompiled workflow markdown to regenerate lockfiles affected by these shared workflow changes (including Kiro/Cursor smoke workflows).

const apiKey =
  process.env.KIRO_API_KEY || process.env.SECRET_KIRO_API_KEY
// and similarly for Cursor:
// process.env.CURSOR_API_KEY || process.env.SECRET_CURSOR_API_KEY

• Fixes [aw-failures] Kiro/Cursor CLI auth fails intermittently — network allow-list gap + missing SECRET_ fallback #50519

[pelikhan]

@copilot commit fixes