GdbHost.exe is now part of the vsix package
Added basic implementation of a executable-finder

This service exposed by BlackBerry package will help the developer to
discover the location of an executable matching the binary running on
target. The same way it gets rid of the ugly data passed via hardcoded
files with build outputs...
Correctly passing an output-path

Now the process-attach feature works perfectly (although there is still
room for improvement by adding custom UI to point to executable).
Fixed a rare crash, when GdbHostRunner exits late

In particular - when AsyncProcessExited() callback is called at the same
time as disposing is performed.
Updated ProjectHelper to also build against VS2010
Updated VSIX manifests to better match expected VS
Optimized displaying message boxes
Removed unnecessary references from BuildTasks
Small DE warnings and field-visibility cleanup
Simplified registry node name for stored settings
Added configurable path to QNX tools

There is now an option to specify path to QNX toolset via system
registry (QNXToolsPath). They don't need anymore to be stored inside
%ProgramFiles(x86)%\BlackBerry\VSPlugin-SDK\qnxtools.
Improved searching for JavaHome
Fixed any-file-dialog forcing .bar extension
Added custom UI, when attaching to process

This UI allows to specify a custom executable to be used, when did not found any
matching project in opened solution. This GREATLY improves the UX, when just attaching
to running processes without full source code available.
Implemented dynamic change of base folders

Since now the developer is not forced to use bbndk_vs at C: drive and
the same about JavaHome and QNX-toolset for basic operations.
They all can change dynamically, however the impact on the rest of the code
is rather hard to predict and more testing is required.
Implemented writing logs into persistent storage
Totally refactored the way VS2012 builds projects
Synchronized msbuild files for VS2013 projects
Added dedicated defs for device/simulator/tablet

It is now possible to distinguish in code between target platform and family.
Fixed names of VS2013 MSBuild files

NOTE: They are renamed on the fly by Visual Studio.
      Sources are shared with VS2012!