Support secret Environment Variables #279
Description
Is your feature request related to a problem? Please describe.
Some variables used in a collection/an environment of it may be a secret value (e.g. a bearer token). I don't want to have them lying around on my file system unprotected or even sync them to git.
Describe the solution you'd like
Use the Safe Storage feature to persist secrets of environments encrypted. At least, they should be stored in the application directory, outside of the collection.json file.
Describe alternatives you've considered
Store them in a ~secrets.json file next to collection.json and create a .gitignore file next to them which ignores any file starting with ~. However, this only works with git.
Additional context
I believe it would be best to store them in a key-value store using a collection ID (string) -> environments (EnvironmentMap) mapping. This simplifies the logic to store and read them.