Env data in output

[narekhovhannisyan]

Types of changes

• Enhancement (project structure, spelling, grammar, formatting)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

A description of the changes proposed in the Pull Request

• Injects env data into output manifest.

[jmcook1186]

this looks great to me. I've checked out the branch and verified locally that:

• the packages in npm list are added to the manifest as a list in execution/environment
• packages installed from github include all the relevant information for recreating the precise install (link with commit hash)
• os and os-version are formatted as expected
• execution command is correctly reported in execution/command

Good to move to QA review