External edit monitoring must respect disabled mode

External edit monitoring wsan't taking into account the possibility that
VsVim was in disabled mode.  In disabled mode there is no need to
monitor for external edits.  Vim is disabled so just let them proceed as
normal in Visual Studio

closes #1375
Added CleanVsix

Added the CleanVsix project to VimAll.sln.  This will allow AppVeyor to
build everything I need to create a build artifact
Do not deploy in AppVeyor builds
Added AppVeyor badge to readme
Fixed readme
Converted readme to markdown
Fixed markdown

Used an actual markdown editor this time to get the MD correct for the
readme
Upgraded to EditorUtils 1.3.1.0

This version supports testing on express SKUs.  This is necessary in
order to run our tests in AppVeyor
Switched to appveyor config file
Fixed KeyDown1 unit test failure

The KeyDown1 unit test was failing because we are unable to set the
keyboard layout to portuguese in AppVeyor.  This isn't actually
necessary to the test anymore though.  It was at one point in the past
when VsVim did interesting querying of keyboard layout.  It no longer
does that hence this feature can simply be removed
Produced an artifact from AppVeyor
Fix exception opening file

Based on the stack trace in this issue it appears another component
triggered a new layout inside the initial LayoutChanged event of an
IWpfTextView.  This change causes the initial mode change logic to
detect this and wait for the next LayoutChanged event before setting up
the initial mode

closes #1376
Added VsixUtil to VimAll solution

The VimAll solution is supposed to contain every project that Vim
development depends on.
Merge remote-tracking branch 'origin/master' into fixes-settings
Removed ILegacySettings

It's been over a year since we transitioned away from application
settings.  No need to keep the migration code around anymore.
Got the TODO up to date
Host customization of global settings
All host options now have a UI element