Description

This PR aims to simplify the usage of "env" files.

Any environment file falls in one of the following categories:
- Example environment files. They serve as a starting point to create your own real environment file.
- Real environment files. They are actual environment files used by the applications inside the repository. They contain private and sensitive information and should never be committed to the repository.
- Preset environment files. They are used by the applications inside the repository, but contain no private or sensitive information. These are generally used to run tests or CI routines.
Rules:
- All example environment files and preset environment files should have the following name: *.env where * can be any string of characters that should describe the usage of the environment file.
- All real environment files that can contain sensitive data should have the following name: .env.* where * can be any string of characters that should describe the usage of the environment file.
- Furthermore, the example environment files must contain appropriate documentation in the form of a clear comment above each variable.
- Preset environment files, that are not used as an example but that contain preset values for a specific use case (example: ci.env), should actually not have documentation included, as they are derived from an actual example environment file, and duplicating the documentation will just add maintenance overhead.

Checklist

Name	Status	Preview	Comments	Updated (UTC)
emojicoin-dot-fun	❌ Failed (Inspect)			Sep 28, 2024 0:13am
emojicoin-dot-fun-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 28, 2024 0:13am