[Feature] [API Keys] Add API key management components, hooks, and actions

[Gautam25Raj]

Summary

This PR introduces a new API key management system with dedicated components, hooks, utilities, and actions for creating, managing, rotating, revoking, and deleting API keys.

This update also improves type safety, state management, and user interaction flows across API key management experiences.

Features

API Key Management UI

• Added new API key management components:
  • API key creation forms
  • API key detail views
  • API key management cards
• Enhanced UI consistency with:
  • New buttons
  • Status badges
  • Interactive cards

Hooks & State Management

• Implemented hooks for:
  • API key creation
  • API key fetching
  • API key state handling
• Improved user interaction and async workflow management

API Key Actions

• Added support for:
  • API key rotation
  • API key revocation
  • API key deletion
• Added user feedback handling for API key operations

Improvements

Types & Utilities

• Added API key record types
• Introduced pagination-related types
• Improved type safety and internal consistency
• Added utility helpers for:
  • API key detail formatting
  • API key data handling

User Experience

• Improved API key management workflows
• Enhanced action feedback and interaction clarity
• Improved component structure and maintainability

Alpha Status

⚠️ Known Limitations

• Some API key flows may still be under active development
• Internal architecture and UI flows may continue evolving
• Additional stabilization work is expected before production release

Notes

• Alpha-stage feature release
• Focused on API key management infrastructure and user workflows
• Additional refinements expected in upcoming releases

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.