Mark NVDA as DPI aware.

This allows us to work with actual screen coordinates rather than scaled coordinates in high DPI configurations. Scaled coordinates seem to be inaccurate in some cases. Also, some accessibiliy implementations don't provide scaled coordinates.
We use the SetProcessDPIAware function rather than using the manifest so it will work when running from source.
Correctly handle apps that aren't DPI aware for display model.

The coordinates provided by these applications are logical coordinates, not physical coordinates as used by DPI aware applications. Convert between logical and physical coordinates where appropriate.
This has to be done using different functions on different versions of Windows, so account for this as well.
Use physical versions of Get/SetCursorPos and WindowFromPoint where available, as these are needed to work with physical coordinates in Windows Vista/7/8.
Oops. We can't call SetProcessDPIAware on Windows XP.
Get/SetPhysicalCursorPos doesn't exist on XP, so still use Get/SetCursorPos there.

Re #3782.
English What's New: Clarify the entry for #3757.
On systems with a high DPI display setting (which occurs by default for many modern screens), NVDA no longer routes the mouse to the wrong location in some applications.

NVDA was made DPI aware to fix this.
Fixes #3758, #3703.
Specifically target Windows 8.1 (and other versions while we're at it) in NVDA's application manifest.

This means that correct Windows version information will be reported on Windows 8.1, rather than reporting as Windows 8.
Fixes #3793.
Fix issues with application profile triggers when creating a virtual buffer fails.

If creating a virtual buffer failed in api.setFocusObject, the global focus variables weren't set, but application triggers were already exited/entered. This meant that next time the focus changed, NVDA tried to exit triggers that had already been exited. Also, there may have been triggers entered that were never exited.
Exceptions from treeInterceptorHandler.update are now caught. Also, the call to handleAppSwitch has been moved as late as possible so other exceptions don't cause this problem. Ideally, there aren't any other possible exceptions like this, but it's best to be safe.
Fixes #3804.
Merge commit 'fetch_head' into jpbranch
fixes ti33140 regarding command quick reference