- After retrieving user set envs from a file, add the system envs back
into the envs object so that envs like PATH, etc… will exist for the
spawned command
- Moved over to using regex for parsing the env file
- Added support for inline comments
- Added support for `key value` pairing file format
- Will now ignore invalid lines in env file, instead of throwing an error
- Removed old test cases
- Added more specific test cases
- Removed the -e/--env flags in favor of just requiring the first arg to
env-cmd to be the relative path to the env file
- Comments are now valid in env files using the #
- Empty lines in env file are now ignored
- Fixed bug env file no longer needs to end on a newline
