Self signed certs

[Shbhom]

used mkcert to generate local SSL certificates inside the nginx/certs directory, and then path binded that directory to /etc/nginx/certs directory inside the container, which I added in the nginx's default.dev.conf

Solving Issue #748

Description 📣

This pull request adds support for local SSL certificates in the development environment. The changes include:

1. Updating the nginx/default.dev.conf file to use locally generated SSL certificates.
2. Adding new certificate files (localhost+2.pem and localhost+2-key.pem) to the nginx/certs/ directory.

These changes will allow developers to run the application locally with HTTPS support, improving the local development experience and making it more closely match the production environment.

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

To test these changes:

1. Install mkcert if you haven't already (installation instructions vary by OS).

2. Generate local certificates using mkcert:

   mkcert -install
   cd nginx/certs/
   mkcert localhost 127.0.0.1 ::1

3. Verify that the nginx/default.dev.conf file has been updated with the correct certificate paths:

   ssl_certificate /etc/nginx/certs/localhost+2.pem;
   ssl_certificate_key /etc/nginx/certs/localhost+2-key.pem;

4. Run the application locally using Docker Compose with the development configuration:

   docker-compose -f docker-compose.dev.yml up

5. Access the application via HTTPS (https://localhost) and confirm that there are no certificate warnings in the browser.

6. Verify that the application functions correctly over HTTPS.

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝