Add AI trust score functionality and document similarity checker

[ojasptl]

AI Functionality

• Implement EnhancedVerification component for calculating AI-powered trust scores.
• Create ErrorDisplay, LoadingDisplay, and ResultDisplay components for better UI feedback.
• Develop SimilarityChecker component to compare two documents for similarity.
• Introduce TrustScoreDisplay component to visually represent trust scores and detailed analysis.
• Add VerificationTrustScore component for document verification against original certificates.
• Implement useAIOperation hook for managing AI operation states (loading, error, result).
• Create aiEnhancedApi.js for handling API requests related to AI enhancements.
• Update authApi.js to improve error handling during user verification.

[vercel]

@ojasptl is attempting to deploy a commit to the Tejas Pokale's projects Team on Vercel.

A member of the Team first needs to authorize it.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	2419a0a	backend/src/services/aiServiceClient.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}