{CI} Remove the aliases of colleagues who have left the team

[jsntcy]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @jsntcy,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[Copilot]

Pull request overview

This PR updates the GitHub policy automation (.github/policies/resourceManagement.yml) to remove auto-assignment/review/notification entries for colleagues who have left the team, keeping PR/issue triage routing current.

Changes:

• Removed requestReview entries for several former team members across multiple service-routing rules.
• Removed assignTo entries (and some addReply notifications) that referenced those former aliases.
• Simplified a number of service-specific rules so they no longer mention departed reviewers/assignees.

[jsntcy]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).