test: add mock integration tests for student resume confirm route

[AMAN194701]

Description

Fixes #6801

Added a dedicated mock integration test suite for the Student Resume Confirm route.

Changes

• Added app/api/student/resume/confirm/route.mock-integrations.test.ts
• Implemented 5 test cases covering:
  • Asynchronous service layer mocking
  • Service loading state rendering
  • Local cache stub verification
  • Fallback procedure validation during timeout scenarios
  • Cache synchronization after successful callbacks
• Verified all tests pass successfully using Vitest.

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

N/A (Test-only changes)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have starred the repo.
• I have made sure that I have only one commit to merge in this PR.

[github-actions]

🚨 Hey @AMAN194701, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod007]

Excellent mock integration tests for the student resume confirm route. Caching and fallback procedures are well covered. However, the CI check is failing. Please resolve the issues and rerun the CI pipeline.