Vim: various smaller fixes and improvements
fixed BuildProject

added RunProject command

better detecting of multiple line type info

updating test results

version number bumb

fixing integration test data

hacky fix for ensuring that newlines are properly intepreted by the auto complete info scratch window
Merge pull request #833 from kjnilsson/dev

Vim - Various smaller fixes fixes + RunProject command.
improve build scripts (Windows)

- add -Full parameter to Build.ps1 to also get dependencies
- add progress information
- replace $STDataPath with $STPackagesPath

Usage:

1) Set $STPackagesPath to Sublime Text's packages path

In order to find out your packages path:
   a) Open Sublime Text
   b) Open the Python console
   c) Type in sublime.packages_path()<RETURN>

2) Run once ./bin/Build.ps1 -verbose -full

That should grab dependencies and publish a version locally.

3) Subsequently, you can simply invoke the script like this:

    ./bin/Build.ps1 -verbose

In case you'd need to get the dependencies again, just run the
script as in step (3).

Other features of Build.ps1 include:

    -Restart: restarts Sublime Text (sublime_text must be on your
     PATH)
    -Clean: wipes the deployment FSharp target folder
    -Debug: stops execution at predefined stages and prints info
Merge pull request #835 from my-personal-forks/fix-build-scripts-windows

improve build scripts (Windows)
add 'go to declaration' command (F12)
add context provider

`ContextProvider` provides contexts to conditionally enable
key bindings.
add license for 'external' lib
refactor
refactor

Add method to parse files from `view` objects.
post completions result to a different result queue

Completions are consumed in a different way, so it
makes sense to post them to a different queue that
only interested consumers should use.
enable completions

- show completions after typing '.'
- show competions in demand when pressing 'ctrl+space'

Completions responses are posted to a completions-only queue
that the completions provider mechanism can consume.

In other words, completion results do not end up in the regular
results queue for other fsac incoming data. This is because
completions must be dealt with synchronously, in contrast to
other fsac commands implemented so far.

Potential pitfalls:

We optimistaclly drain the completions queue when fsac takes time
to respond, but this may potentially cause inconsistent results.
add tooltip request
add ErrorInfo wrapper class to access error info items
enable tooltips, errors

- access tooltips via Ctrl+., Ctrl+. menu
- highlight errors in real time
fix typo
refactor

- add comments
- robustify
- add better logging
re-raise unhandled errors
fix method call
fix bug: don't send ProjectRequest too often
send project request when no project has been yet set