Migrate copilot-requests feature flag to permission and recompile

The `features.copilot-requests: true` flag is a deprecated shorthand that
is inert unless migrated. Run `gh aw fix --write` to rewrite it to
`permissions.copilot-requests: write` in all 11 workflow sources, then
recompile so the lock files inject the GitHub Actions token auth and
`S2STOKENS: true` that actually enable org billing at runtime.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 004ba78d-3cf4-41ab-8647-180e683460f0

Author: SteveSandersonMS

.github/workflows/cross-repo-issue-analysis.lock.yml

@@ -1,6 +1,4 @@
 ---
-features:
-  copilot-requests: true
 description: Analyzes copilot-sdk issues to determine if a fix is needed in copilot-agent-runtime, then opens a linked issue there
 on:
   issues:
@@ -16,6 +14,7 @@ permissions:
   contents: read
   issues: read
   pull-requests: read
+  copilot-requests: write
 steps:
   - name: Clone copilot-agent-runtime
     env:
@@ -114,4 +113,4 @@ Classify the issue into one of these categories:
 2. **Err on the side of creating the runtime issue**: If there's a reasonable chance the fix is in the runtime, create the issue. False positives are better than missed upstream bugs.
 3. **Link everything**: Always cross-reference between the SDK issue and runtime issue so maintainers can follow the trail
 4. **Be specific**: When describing the root cause, point to specific files, functions, and line numbers in both repos
-5. **Don't duplicate**: Before creating a runtime issue, search existing open issues in `github/copilot-agent-runtime` to avoid duplicates. If a related issue exists, reference it instead of creating a new one.
+5. **Don't duplicate**: Before creating a runtime issue, search existing open issues in `github/copilot-agent-runtime` to avoid duplicates. If a related issue exists, reference it instead of creating a new one.