Do not try to register PZP with itself

This makes registerSender throw an exception if its from and to params
are the same, as it is not useful to try and register with itself. This
change makes it possible to bypass the following bug.

PZP code assumes the TLS port to connect with other PZPs is always the
same. Thus when using two PZPs on one host, these two cannot directly
connect as the port will be taken by the first. And the first PZP will
connect to itself.

Jira-issue: WP-250
Force set device name

Makes it possible to set the device name for a PZP with
--force-device-name=NAME upon startup. This is needed, so it's possible
to start more than one PZP on a single host as the device name will be
based on the hostname by default. The commit changes the various config
methods that are called to pass that custom device name and use it.

It became appearant that sometimes device name and friendly name are mixed
up and can mean the same. This commit changes the code for the PZP to only
use a device name, the friendly name might be only stored in the config
file, but never displayed. For the PZH friendly name is still essentially
the device name.

Also removes some no longer used arguments from the PZP start up script.

Jira-issue: WP-250
Added AppLauncher API for Android

Supporting URLs that will be loaded using native browser / browser intent. Widget support follows in later versions.

Jira-issue: 559
Merge pull request #298 from andrepaul/WP-559-AppLauncherAndroidImplUsingURLs

Added AppLauncher API for Android
Merge pull request #283 from aldafu/WP-250-multiple-pzp-on-single-host

Wp 250 multiple pzp on single host
Merge pull request #299 from krishnabangalore/master

wp-542
Use "window" instead of "this"

In strict mode "this" inside a function doesn't become the window object.
Functions need to explicitely called with context. To avoid this, we use
the window object directly instead of "this". That's what non strict mode
does anyway.

Jira-issue: WP-564
Added actuator API

first properitary actuator API implemenation that assumes IoT hardware that reacts on REST calls using /a=x,y,z where x,y,z are floats as URL path

Jira-issue: WP-233
Merge pull request #300 from aldafu/WP-564-use-window-obj-instead-of-this-obj

Use "window" instead of "this"
Merge pull request #301 from andrepaul/WP-233-ActuatorAPI

Added actuator API
WP-500: local contacts local uri pictures bug fixed
Correct path for Widiget Manager

Jira Issue: WP-568
Merge pull request #305 from ziransun/WP-568

Correct path for Widiget Manager
platform allignement
WP-500: local contacts local uri picture bugs fixed
Updates XMPP to the new folder structure.

Jira issue: WP-213
Merge pull request #307 from eelcocramer/wp-213

Updates XMPP code conform the new folder structure.
Add grunt build file

Grunt is a task based build system based on NodeJS.

Install grunt globally with: npm install -g grunt
This makes sure grunt is added to your PATH.

This commit adds the grunt.js build file which comes with the these targets:
 * default - call without target name, an unminified webinos.js file is built
 * minify - builds webinos.js and a minified webinos.min.js.
 * clean - removes both generated files from minify target
 * clean-certs - removes the certificate directories in ~/.webinos

To generate webinos.js simply run: grunt
in the root directory.

Jira-issue: WP-202
Remove old webinos.js build files

The grunt build system is used now. Update package.json to call grunt on
install.

Jira-issue: WP-202
Added test page for Device Orientation API

Jira-issue: WP-569