Deploying module is a bit funky until dotnet-cli gives us more control
over which libraries to build and where. Theoretically we'll be able to
package System.Management.Automation and depend on the package instead,
so Commands.Omi can be its own project entirely.
Cleaned up the Commands.Omi project.json as it had some unnecessary
cruft from where it was copied. Also removed the AssemblyInfo as it does
not matter for a new module.
Moved the Get-OmiInstance Pester test to the project's test folder so it
doesn't run with our suite of tests (as it takes a dependency on OMI).
Need the up-to-date version so that exiting the console doesn't totally
mess up the hosting shell (Bash).
Should not depend on this package longterm, as it's
platform-specific. Tracking in https://github.com/dotnet/cli/issues/405
Andrew Schwartzmeyer