override values from .env with values form environment variables

[aakashsigdel]

according to dotenv documentation:

What happens to environment variables that were already set?
We will never modify any environment variables that have already been set. In particular, if there is a variable in your .env file which collides with one that already exists in your environment, then that variable will be skipped. This behavior allows you to override all .env configurations with a machine-specific environment, although it is not recommended.

What this PR does:

• if a value is present on environment variable it overrides the value that is on the .env files

Why is this needed:

• to align more with how dotenv lib functions
• to make it easier for CI/CD piple to define the env vars

fixes #37

[goatandsheep]

this is a pretty essential PR imo. This package is unusable without this.

[goatandsheep]

This package is inactive. I say you start a new package.

[chandlervdw]

🙏 please get this merged

[solomonhawk]

Anything I can do to help move this along?

[goatandsheep]

@solomonhawk There's a new repo and package babel-plugin-dotenv-import. Please reopen in the new repo