dep-review workflow fails to request review: "Could not resolve" openvmm-dependency-reviewers team

Summary

The Dependency Review workflow (.github/workflows/dep-review.yml) fails on every PR that introduces external Cargo dependency changes. The script in .github/scripts/dep-review.js calls pulls.requestReviewers for the team microsoft/openvmm-dependency-reviewers, and GitHub responds with a 422:

RequestError [HttpError]: Validation Failed: "Could not resolve to a node with the global id of 'T_kwDOAF3p4s4AqrNG'."
    at async run (/home/runner/work/openvmm/openvmm/.github/scripts/dep-review.js:338:5)

POST URL: https://api.github.com/repos/microsoft/openvmm/pulls/<n>/requested_reviewers
Body: {"team_reviewers":["openvmm-dependency-reviewers"]}

The unhandled error fails the workflow step and blocks the PR's required check.

Affected runs

Every recent failure of the Dependency Review workflow was hit by this. A few examples:

• https://github.com/microsoft/openvmm/actions/runs/25813615611 (PR #3470, bump-openssl-0.10.79)
• https://github.com/microsoft/openvmm/actions/runs/25815984486 (crypto-rust)
• https://github.com/microsoft/openvmm/actions/runs/25803692745 (crypto-rust)
• https://github.com/microsoft/openvmm/actions/runs/25776874131 (cca-dev)
• https://github.com/microsoft/openvmm/actions/runs/25753065819 (smmu)

PRs without external dep changes pass because the team-request branch in the script is never reached.

Likely cause

The team slug openvmm-dependency-reviewers (under the microsoft org) is no longer resolvable by the workflow token \u2014 most likely the team was deleted, renamed, or had its repo access removed. A stale cached node ID (T_kwDOAF3p4s4AqrNG) shows up in the error message.

Suggested fix

One of:

1. Recreate / restore access for the microsoft/openvmm-dependency-reviewers team.
2. Update DEP_REVIEW_TEAM in .github/scripts/dep-review.js to a team that exists and is accessible to the workflow.
3. Wrap the requestReviewers call in a try/catch so a missing team doesn't fail the check (and surfaces a warning instead).

Option 3 alone would unblock PRs immediately even if the team situation is still being sorted out.

Start with .github/workflows/dep-review.yml and .github/scripts/dep-review.js around line 338, then inspect DEP_REVIEW_TEAM and the linked failing workflow runs. Confirm how the reviewer-request path should behave when the team cannot be resolved; done means dependency-review PRs no longer fail solely because of this request and the intended reviewer handling is verified.