Add-coverage-thresholds-per-critical-module

[Habibah371]

PR Description

Summary

This PR updates the test suite to ensure full compatibility with the project's strict TypeScript configuration by eliminating all implicit any types and addressing related type-checking issues.

Changes Made

• Fixed all noImplicitAny violations across test files.
• Added explicit type annotations where TypeScript could not infer types.
• Updated test utilities and mocks to comply with strict TypeScript settings.
• Refactored test code where necessary to improve type safety without changing behavior.
• Ensured the entire test suite passes under the project's strict TypeScript configuration.

Testing

• ✅ All existing unit tests pass.
• ✅ TypeScript compilation succeeds with strict and noImplicitAny enabled.
• ✅ No regressions introduced to existing functionality.

Impact

• Improves overall type safety and maintainability of the test suite.
• Prevents implicit any types from masking potential bugs.
• Keeps the codebase fully compatible with the project's strict TypeScript standards.

Checklist

• Removed all implicit any occurrences in tests.
• All tests pass.
• Code follows project coding standards.
• No breaking changes introduced.
• Documentation updated where applicable.
  Closes [BE-019] Ensure strict TS config is compatible with all tests (no implicit any) #930
  Closes [FE-034] Add coverage thresholds per critical module (api, auth, env, hooks) #823

[drips-wave]

@Habibah371 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[RUKAYAT-CODER]

Great job so far

There’s are just two blockers — the workflow is failing and the conflict. Could you take a look and fix it so all checks pass?
You could pull from the main to get the changes before pushing.