Add multiple environment support and cleanup

[hassancodess]

This PR includes the following updates:

• Improved formatting for environment variables validation errors.
• Replaced dotenv with dotenvx.
• Added development and production scripts to package.json.
• Updated README with instructions for .env.development and .env.production.
• Added .env.development and .env.production to .gitignore.

Summary by Sourcery

Add support for multiple environments by introducing .env.development and .env.production files, and update the README with relevant instructions. Replace dotenv with dotenvx for better environment variable management and improve error formatting for environment variable validation.

New Features:

• Introduce support for multiple environments by adding .env.development and .env.production files.

Enhancements:

• Improve formatting for environment variables validation errors using a custom pretty print function.
• Replace dotenv with dotenvx for environment variable management.

Documentation:

• Update README with instructions for setting up .env.development and .env.production files.

Chores:

• Add .env.development and .env.production to .gitignore to prevent them from being tracked in version control.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request enhances the project's environment configuration management by introducing support for multiple environments, improving error handling, and updating the project setup process. The changes focus on replacing the dotenv library with dotenvx, implementing a more user-friendly error display for environment variable validation, and updating the README with new instructions for environment setup.

File-Level Changes

Change	Details	Files
Replaced dotenv with dotenvx for improved environment variable management	Imported dotenvx instead of dotenv Updated configuration loading to use dotenvx.config()	src/config/config.service.ts
Implemented improved error handling and formatting for environment variable validation	Added a prettyPrintErrors function to format ZodError objects Updated config parsing to use safeParse instead of parse Added error logging and process termination on validation failure Exported config.data instead of raw config object	src/config/config.service.ts
Updated README with instructions for multiple environment setups	Changed instructions to create .env.development and .env.production files instead of a single .env file Updated the environment variable setup section to reflect the new multi-environment approach	README.md

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

Hey @hassancodess - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟡 Security: 1 issue found
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

🚨 suggestion (security): Review usage and security implications of new dependencies

New dependencies like '@dotenvx/dotenvx' and '@noble/ciphers' have been added. Ensure their usage aligns with project requirements and doesn't introduce security vulnerabilities.