Integrate backend API with frontend UI and add tests

[gretlee]

Summary

This PR extends the backend, updates the frontend, and wires them together.

Changes Made

• Backend: Added new endpoints for [explain what you built, e.g., user authentication / data retrieval].
• Frontend: Connected the UI components to the new backend endpoints using [e.g., Axios/Fetch].
• Wiring: Implemented state management to handle the API responses.
• Testing: Added unit tests for the backend and integration tests to verify the frontend-backend communication.

How to Test

1. Checkout this branch.
2. Run npm install (or your package manager).
3. Start the server and open the UI.
4. Verify that [mention a specific feature] works as expected.

Related Issues

Closes #[Issue Number] (if applicable)

[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.

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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	MongoDB Credentials	c88539a	CommBank-Server/Secrets.json	View secret
-	-	MongoDB Credentials	89df7b0	CommBank-Server/Secrets.json	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.}