feat: db changed to postgres

[maanasb01]

This PR resolves issue #613.

Changes:

• Replaced the Docker image of MySQL with the Postgres image.
• Updated the API_Server codebase to work with Postgres instead of MySQL. The required changes were minor and primarily made in the config file.
• I, along with @aatmanvaidya, tested the Postgres database locally. All basic CRUD operations and other relevant operations functioned as expected. Additionally, we regenerated the production database dump locally on the new Postgres database, and everything seemed to have worked properly.

Other Changes in the docker-compose file:

• Added a line in the "volumes" section to persist the node_modules folder. Previously, the npm install command in the API_Server Dockerfile required dependencies to be installed locally. This change ensures dependencies are available without needing local installation.
• I encountered errors when running the docker compose up command. By commenting out the line command: tail -f /dev/null, everything worked smoothly. This line is still commented out as it may have been causing issues by overriding the default startup command.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [2074360](https://dashboard.gitguardian.com/workspace/54491/incidents/2074360) | Triggered | Generic Password | 3663a1052af5ecff9776fd4a72bd59a9f5021a3a | browser-extension/docker-compose.yml | [View secret](https://github.com/tattle-made/Uli/commit/3663a1052af5ecff9776fd4a72bd59a9f5021a3a#diff-a9c78d2508853eef4c93afd9ac185ff9b9f4922bb02b0d32514f9030ccd8504aR9) |

🛠 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 secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.}

[dennyabrain]

Oh, nice! i was hoping the changes to be this minimal.