feat: Add emergencyVerify and revokeVerification management functions to IIdentityManagerV2

[2PykeETH]

Summary

This PR extends the IIdentityManagerV2 interface with two new external functions — emergencyVerify and revokeVerification.
These additions enhance the administrative control and operational resilience of the identity verification system by introducing emergency verification pathways and explicit verification revocation capabilities.

---

Changes

🧩 New Functions

1. emergencyVerify(address user, UserType userType, VerificationLevel level)

• Purpose:
  Provides administrators with a controlled override mechanism to verify users immediately in urgent or exceptional scenarios (e.g., failed proof submissions, compromised verification circuits, or protocol recovery events).

• Parameters:

  • user — address of the user being verified.
  • userType — classification of the user (e.g., STUDENT, VERIFIER, ADMIN).
  • level — the verification level to assign (e.g., DEVICE, ORB).

• Expected Behavior:

  • Bypasses standard proof-based verification.
  • Restricted to admin-level access.
  • Emits a UserVerified event for transparency.
  • Used only under special operational or governance-approved conditions.

---

2. revokeVerification(address user, string calldata reason)

• Purpose:
  Allows authorized entities (e.g., admins or verifiers) to revoke a user’s existing verification, ensuring integrity when a user’s credentials are compromised or invalidated.

• Parameters:

  • user — address whose verification is being revoked.
  • reason — textual reason for revocation, aiding on-chain auditability.

• Expected Behavior:

  • Updates user’s verification record to unverified.
  • Emits a UserVerificationRevoked event with the reason logged.
  • Prevents further access to verification-restricted features until reverified.

---

Motivation

• Security: Provides emergency fail-safes for administrative control in critical scenarios.
• Governance: Enables transparent revocation of user verification with auditability.
• Resilience: Allows for rapid remediation during system failures or identity breaches.

---

Implementation Notes

• Access control should restrict both functions to authorized roles (onlyOwner or governance roles).
• Consider adding timelocks or cooldowns to emergencyVerify for governance safety.
• Ensure consistent event emission (UserVerified, UserVerificationRevoked) across all verification pathways.
• Include NatSpec comments when implementing the logic in the main IdentityManagerV2 contract.

---

Next Steps

• ✅ Implement function logic in IdentityManagerV2.sol.
• ✅ Add role-based access control (onlyAdmin, onlyOwner).
• ✅ Add comprehensive test coverage for:
  • Successful emergency verifications.
  • Revocation flow with valid and invalid users.
  • Event emission and state update verification.
  • Attempted unauthorized calls.