Revert "copilot-requests: write" opt-in for Copilot CLI inference

PR #1469 added `copilot-requests: write` to the java-interop-reviewer
workflow permissions block to opt into the new feature where gh-aw uses
the built-in GITHUB_TOKEN for Copilot CLI inference, with AI credits
billed to the org.

That feature requires the "Allow use of Copilot CLI billed to the
organization" Copilot policy to be enabled at the org level. The dotnet
org has not enabled that policy yet, so the workflow now fails with HTTP
403 from api.githubcopilot.com/models. See failing run:
https://github.com/dotnet/java-interop/actions/runs/27628125187/job/81695629467

Revert just the opt-in line in java-interop-reviewer.md and recompile
the lock file. After this merges, the COPILOT_GITHUB_TOKEN secret needs
to be re-added to the copilot-pr-reviewer environment so the PAT-based
flow works again.

Also revert max-ai-credits from 100M back to -1 (truly unlimited). PR
#1472 capped it at 100M based on a wrong theory that -1 was causing the
auth 403; that 403 reproduced under 100M too, so the cap wasn't the
issue and the user prefers -1.

The gh-aw CLI v0.79.8 bump and the agentics-maintenance.yml updates
from PR #1469 are intentionally left in place.

See: https://github.blog/changelog/2026-06-11-agentic-workflows-no-longer-need-a-personal-access-token/

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jonathanpeppers

.github/workflows/java-interop-reviewer.lock.yml

@@ -7,13 +7,12 @@ on:
 environment: copilot-pr-reviewer
 permissions:
   contents: read
-  copilot-requests: write
   pull-requests: read
 engine:
   id: copilot
   model: claude-opus-4.8
 max-daily-ai-credits: -1
-max-ai-credits: 100M
+max-ai-credits: -1
 network:
   allowed:
     - defaults