Use .env file or secrets manager instead of declaring environment variables in launch.json for Cloud Run Emulator

[Manny]

Use case
I would like to use environment variables or the secrets manager to set the environment variables while running Google Cloud run emulator.

Alternatively, let us use something similar to "runArgs" in devcontainer.json so we can use ["--env-file"," FILENAME.env"],

Feature
This would allow me to commit launch.json into GitHub without exposing sensitive passwords and keys.

I already have a .env file, so it would make it simpler to have only one place to update these environment variables

[Sri Pasumarthi]

Thank you for the suggestion. We have registered this request and will prioritize appropriately.