[refactor] implement dotenv to hide api-keys from codebase

[opxdelwin]

Description

This PR will add a .env file to securely store these credentials. The code now retrieves them from the environment variable, keeping them hidden within the development environment.

Here's what this means:

• Improved security: Credentials are no longer directly exposed in the code.
• Separate testing setup: Developers can easily create their own Firebase and Appwrite projects for local testing without needing real credentials.

Fixes #273

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Refactor (does not change functionality, e.g. code style improvements, linting)
• [x] Documentation update

How Has This Been Tested?

I haven't added unit tests as these are code refactors, moreover it doesn't look like tests have been initialized beforehand. I'll be happy to add if required.

Checklist:

• [ ] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings

Maintainer Checklist

• [ ] closes #xxx
• [ ] Tag the PR with the appropriate labels

[opxdelwin]

As of now, API keys of the production server are exposed, which might have been unintended. This could lead to exploitation of resources and incur unexpected costs. That is why we prefer .env while initialisation of any project.

Secondly, But then, later when we're to run automation to publish releases straight to the respective platform, or run checks on PR and commits, removing this file from the codebase would raise issues.

[Aarush-Acharya]

Hey @opxdelwin Thanks a lot for your contribution 🚀✨,

having a .env is always considered as on of the best practices for any repository. But currenlty we planning to have a .bat script that creates an appwrite env similar to our main env on the contibutors local machine using appwrite self hosted (docker). Thus we wont have to expose our env variables anymore rather more control would be in the contributors hands.

We really appreciate your work towards Resonate. There are a lot of issues and things to be done in the app. Lets move forward and build Resonate a beautiful app.

Thank you