feat: Add external view verification status functions to IIdentityManagerV2 interface

[2PykeETH]

Summary

This PR introduces three new external view functions to the IIdentityManagerV2 interface, enhancing the contract’s ability to expose user verification states for off-chain applications, frontend dashboards, and inter-contract integrations. These functions standardize access to verification data and improve composability across the verification system.

---

Changes

🧩 Added View Functions

getIsVerified(address user) external view returns (bool);

• Returns whether a given user currently holds a valid verification.
• Designed for simple verification checks in frontends or off-chain services.

isUserVerified(address user) external view returns (bool);

• Provides a semantic alias for verification validation, useful for internal or external contract calls that follow naming conventions consistent with existing identity modules.

isVerificationExpired(address user) external view returns (bool);

• Returns whether a user’s verification has expired based on their expiration timestamp.
• Useful for periodic audits, automated renewals, and backend monitoring systems.

---

Motivation

The goal of these additions is to improve clarity and accessibility of verification-related state without requiring developers to manually inspect storage or event logs.

Benefits:

• ✅ Simplifies on-chain and off-chain verification logic.
• 📊 Enables efficient integration with dApp frontends and analytics layers.
• 🧠 Promotes modularity by decoupling verification checks from administrative functions.
• 🔒 Improves security transparency through explicit and readable verification queries.

---

Implementation Notes

• All functions are external view, ensuring no gas cost for read-only off-chain calls.
• Consistent naming scheme aligns with IIdentityManagerV2 interface conventions.
• Follows Solidity documentation and forge fmt formatting standards.

---

Next Steps

• Extend internal implementation in IdentityManagerV2 contract to map these interfaces to state logic.
• Add unit tests verifying correct return values for active, inactive, and expired users.
• Integrate into the frontend identity status component for real-time verification visibility.