Add device payloads for second pilots

Device payloads for second pilots consites in:

* Payload for Windows and Linux with NVDA and Windows Magnifier:
** new file:  testData/deviceReporter/secondPilots/platformAB_onWindows_NVDA.json
* Payload for Windows and Linux with SuperNova (screen reader and magnifier)
** new file:  testData/deviceReporter/secondPilots/platformAB_onWindows_Supernova.json
* Payload for Android with Talkback
** new file:  testData/deviceReporter/secondPilots/platformAB_onAndroid_TalkBack.json
* Payload for Android with MobileAccessibility
** new file:  testData/deviceReporter/secondPilots/platformAB_onAndroid_MobileAccessibility.json
* Payload for Demo GoogleChrome
** new file:  testData/deviceReporter/secondPilots/demo_GoogleChrome.json
* Payload for Demo Maavis
** new file:  testData/deviceReporter/secondPilots/demo_Maavis.json
* Payload for Demo SmartHouse
** new file:   testData/deviceReporter/secondPilots/demo_SmartHouse.json

Resolves: http://issues.gpii.net/browse/GPII-337
Add missing pilot device payload

Added device payload for scenario library and multipleSolutions
Fix indentation level in demo_MultipleSolutions
Fix indentation level ...

for platformAB_onAndroid_MobileAccessibility
remove blank lines and  the wrong ","
GPII-103: Updated all the NP sets and the solution registry to not include the datatype in preferences but instead have them defined in the options block
GPII-103: While not strictly GPII-103, it seemed sensible to clean up the cursor transformations by using quantize functions instead of the previous condition/op combo
Activate Talkback when ScreenReaderTTSEnabled common term is set
GPII-828: Added entry with a few transformations
GPII-828: Added json files for acceptance tests
GPII-828: Added a missing NP set for acceptance tests, and reset installed solutions to contain its proper value
GPII-103: Corrected roger.json which had drifted from the correct value space for this setting (apparently numeric, range 0-1.0)
Merge branch 'GPII-103'

* GPII-103:
  GPII-103: Corrected roger.json which had drifted from the correct value space for this setting (apparently numeric, range 0-1.0)
  GPII-103: While not strictly GPII-103, it seemed sensible to clean up the cursor transformations by using quantize functions instead of the previous condition/op combo
  GPII-103: Updated all the NP sets and the solution registry to not include the datatype in preferences but instead have them defined in the options block
Merge remote-tracking branch 'javihernandez/master-screenReaderTTSEnabled-android'
GPII-872: Working linted version with updated Gruntfile
GPII-873: Fix for faulty ontologising mapping within matchmaker, wrong order of arguments in AcceptanceTests, removed smarthouses from default device reporter payload
GPII-873: First working "consolidated test" verifying ontologised and inverseCapabilities logic applied to preferences set os_win7
GPII-873: Consolidated inverse capabilities tests completed, updated Infusion and jqUnit dependencies, corrected namespaces in some other tests
GPII-873: Improvements to Linux solutions - use quantize and linearScale transforms for better future invertibility
GPII-873: Corrected input path of linear scale transform for text-scaling-factor