Fix #99 - completion in remote sessions

When powershell has entered a remote session via Enter-PSSession,
completion was completing against the local session.

The fix is to use the remote runspace when calling the completion
api.  The remote runspace isn't exactly exposed in a clean way
from the host, so the fix is mixed between a bit of PowerShell
and C#.
Add key bindings in Windows mode

Windows mode now has by default:
    * Interactive history search (Ctrl+R/Ctrl+S)
    * DigitArgument (Alt+Num)
Support digit args for word/character movement
Cleanup some Resharper issues
HistoryNoDupes to store but not recall dupes

HistorySearch and InteractiveSearch still need work though
HistoryNoDupes - Search/InteractiveSearch History
Change eol behavior for NextWord/ForwardWord

Cmd and bash place the cursor at the end of the last word
instead of one past the end of the word when moving by word.

PSReadline emulated that behavior, but it's inconsistent with
word movement on the rest of the line and it's inconvenient
because you typically need to use the right arrow or end
to edit at the end of the line.

I've removed the emulated behavior, the cursor will now move
to the end of the line.
HistorySearch changed to use emphasis

Like interactive search, history search now uses emphasis
to make it obvious what is being searched.  With this change,
the cursor will also always move to the end as it's much
less useful to have the cursor near the start of the line.
Add api to get selection state.
Fix script for moved files
Revert "Use runtime check to allow other console-based hosts to use PSReadline."

This reverts commit f5c94f7fe2da695190cc2584c32695f0eb7d8de7.

Conflicts:
	PSReadLine/PublicAPI.cs
Update for release
Merge remote-tracking branch 'upstream/master'

Conflicts:
	PSReadLine/History.cs
	PSReadLine/Movement.cs
	PSReadLine/PSReadLineResources.resx
	PSReadLine/UndoRedo.cs