Use Internal PowerShell Host

[ferventcoder]

This involves really designing the process and I have ideas in head for this one so restricting this to core team only.

Implement a custom PowerShell host. This allows for the following:

• Read-Host, Prompt for Choice, etc times out when running with confirm prompts so that the host
  doesn't block forever. It also allows the default to automatically be
  selected.
• ReadKey timeouts when running with confirm prompts.
• Write-* values all get logged with the choco log all in the proper
  location instead of needing to parse the values to determine which
  log they should go to.
• Write-Progress shows up inline.

By default use the internal PowerShell host. Allow using the system
host either by shutting off the feature or by using a switch
--use-system-powershell.

When running PowerShell operations, use a built-in PowerShell host by
default, allowing fallback to the older method of running Posh
by calling an external process. By building against the oldest version
of System.Management.Automation that aligns with the oldest Windows
Operating Systems supported, we can guarantee this will work on every
version of Windows where Chocolatey is supported.

In case we do run into issues, attempt to resolve the PowerShell
assemblies starting from the newest version and falling down to the
older versions until one is resolved or no version is resolved. There
is a known assembly that will go through this process every time -
System.Management.Automation.resources, en-US. To see those assemblies
go through, one must ask for both debug and verbose output.

This reverts the changes for GH-249 in 9936876 and the changes
from GH-349 in 344268b so that both paths (system powershell
and choco's built-in PowerShell) run with similar output and because by
default in d523e7b (GH-445) choco no longer fails on the
presence of stderr output.