Token-type specific credential revocation and de-authorization actions [GA]

### Value Prop
When a security incident strikes, you can now revoke specific types of credentials—such as all personal access tokens or all SSH keys—without disrupting every other token in your organization or enterprise. Organization admins also gain the same bulk revocation controls that were previously only available to enterprise owners, so you can respond quickly at the level where you actually manage day-to-day access. This gives security teams a faster, more targeted way to contain credential compromise with minimal collateral impact.

### Expected Outcome
Teams responding to credential incidents will spend less time manually hunting down individual tokens and less risk over-revoking credentials that don't need to be touched. By bringing token-type granularity and org-level parity to bulk revocation, GitHub aims to reduce the blast radius of self-serve incident response and help organizations contain threats more efficiently. The result is a more precise, less disruptive security workflow for enterprise members, org admins, and enterprise owners alike.

This roadmap issue describes token-type-specific credential revocation and organization-level de-authorization, but it names no repository files, tests, or implementation entry points. Research would need to identify the relevant GitHub security and access-control systems first; done would mean targeted bulk revocation works for the stated credential types without affecting unrelated credentials.

Written by the indexing model from the issue text.