feat: implement security and tooling enhancements

[Georgechisom]

This PR implements four critical security and developer tooling improvements to enhance code quality and application security.

Changes include pre-commit hooks with lint-staged and commitlint to enforce consistent code formatting and conventional commit messages. CSRF protection has been added using the double-submit cookie pattern to prevent cross-site request forgery attacks. API versioning middleware now supports deprecation management with sunset policies and proper client notification headers. Account lockout functionality implements progressive delays after failed authentication attempts to mitigate brute force attacks.

The pre-commit hooks automatically lint and format code before commits while commitlint validates commit message format according to conventional commits specification. CSRF tokens are generated server-side and validated on state-changing requests with both frontend and backend implementations provided. API versioning extracts version from path, header, or query parameter with deprecation warnings and sunset date enforcement. Account lockout uses Redis to track failed attempts with exponential backoff delays that increase progressively to slow down attackers.

All implementations follow production-ready patterns with comprehensive error handling and are designed for easy integration into the existing codebase without breaking changes.

Closes #759
Closes #752
Closes #753
Closes #755

[vercel]

@Georgechisom is attempting to deploy a commit to the smartdevs17's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Georgechisom 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

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 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.}}