GPII-413: Add a dynamic Device Reporter 

Related literature about this can be found [here], and can be tested with [this pull request to GPII/linux].

The implementation follows a similar approach to how the settingsHandlers work.
Here you can see how a solution entry should be written in order to call to a deviceReporter plugin.

<pre>
{  
    "name": "ORCA Screen Reader",
    "id": "org.gnome.orca",
    "contexts": {
    "OS": [{
        "id": "linux",
        "version": ">=2.6.26"
    }],
    "deviceReporters": [
        { 
            "type": "gpii.packageKit.find",
            "name": "orca"
        }
    ]
}
</pre>

For this first example I have used the packageKit module for GNU/Linux  but we could create a few common deviceReporter plugins such as:
* A DR plugin that could look for a file in the filesystem, ie, look for /usr/opt/bin/google-chrome
* A DR plugin that could check if a process is running on the system, ie: firefox

Inspired by [this], and as a replacement for the Linux' packageKit module in Windows, a node module can be built in order to poke the Windows registry for installed solutions.

Any testing/feedback will be awesome :)
Cheers!

  [here]: http://issues.gpii.net/browse/GPII-413
  [this pull request to GPII/linux]: https://github.com/GPII/linux/pull/49
  [this]: http://stackoverflow.com/a/1458550
This test and iteration can be condensed by writing 

fluid.each(entry.contexts.deviceReporters, function (deviceReporter) { 
.....