Disable threat detection in agentic workflow

[cheenamalhotra]

Addresses #4400

Detection flow doesn't fetch access token from environment, and requires copilot token from repository, this is why we cannot get it working in a protected environment configuration.

We are now allowed to keep PATs, so the only option is to disable detection till we get to next stage. Disabling this till we get org-level copilot access setup in GitHub Actions.

[Copilot]

Pull request overview

Disables the agentic workflow threat-detection path for the issue-triage workflow so it can run under a protected GitHub Actions environment configuration that restricts token access.

Changes:

• Added workflow comments documenting why the issue-triage environment is set and why threat detection is disabled.
• Disabled threat detection in the workflow’s safe-outputs configuration.
• Regenerated the compiled .lock.yml to remove the detection job and related steps/dependencies.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/issue-triage.md	Documents protected-environment behavior and disables threat detection via safe-outputs.
.github/workflows/issue-triage.lock.yml	Compiled output reflecting the removal of threat-detection logic and dependencies.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.