Chore/mobile/refactor testing for mobile

[u21631532]

Description

This pull request implements a new feature for user authentication using JWT tokens. The changes include:

1. Updating the user login and registration endpoints to use JWT
2. Implementing middleware for protected routes that require authentication

This change improves the security of our application by replacing the old session-based authentication with a more scalable token-based approach.

Fixes #255

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

The following tests were conducted to verify the changes:

• Unit tests for AuthService, APIService,Navbar,User,Bookings, Notifications etc.' methods (token generation, validation)
• Integration tests for login and registration endpoints
• End-to-end tests for protected routes

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• 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

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13149987	Triggered	Generic Password	7ba4f7f	frontend/occupi-mobile4/services/authservices.ts	View secret
13149987	Triggered	Generic Password	5c4f173	frontend/occupi-mobile4/services/authservices.ts	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}