[SysApps][Android] Fix several issues on messaging api

1) Correct addEventListener from "messaging" to "messaging.sms".
2) Each PendingIntent should have different requestCode to identify itself. If
using same code, the extra data field of PendingIntent instance will be replaced
by the new one. Then system calls the intent callback function only once.
3) In unit test page, move the verification steps into send.then
callback instead of calling after send function.

BUG=https://crosswalk-project.org/jira/browse/XWALK-940
[Linux][Tizen]Fix the bug XWALK-956:Remote debugging not work in crosswalk/Tizen_IVI.

Set IP address in commandline to INADDR_ANY instead of "127.0.0.1".
This allowed the server to receive packets destined to any of the interfaces.

BUG=https://crosswalk-project.org/jira/browse/XWALK-956
[Runtime] Generate the WGT package id by settings in config.xml.

For WGT package, the package id in Crosswalk runtime should be generated
from the settings (id attribute in widget (W3C widget) or
application (Tizen widget) element) in config.xml, instead of generating
from a randomly temporary directory path, so that one package should be
identified by its id.
Merge pull request #1585 from shawngao5/master

[Android] Fix unable to get the "messaging" permission on Android OS
Merge pull request #1628 from takethathe/wgt_id

[Runtime] Generate the WGT package id by settings in config.xml.
Merge pull request #1620 from iKevinHan/remotedebuging

[Linux][Tizen]Fix the bug XWALK-956:Remote debugging not work
[Runtime] Separate WGT application manifest handling from XPK applications.

When loading WGT manifest file, current Crosswalk maps XML Widget
elements to manifest keys under namespace 'application_manifest_keys' by
hard code. Consequently, WGT app and XPK app share the same manifest
keys and manifest handlers. As with more manifest keys and handlers are
introduced for WGT app, this causes a mix up of WGT specific keys and
XPK specific keys, due to WGT and XPK app have different manifest formats
and keys, especially put Tizen Extending Configuration Elements into
consideration.

A solution to fix above issue is to separate WGT manifest keys and handlers
from XPK apps. In detail, when loading WGT manifest, we introduce a
mechanism to save XML configuration information into manifest Dictionary
structure(note that this is not hard code mapping), keys are different
from those of XPK apps. WGT keys are put under 'application_widget_keys'
namespace, while XPK keys are put under 'application_manifest_keys'.
Then we could add WGT specific handlers for WGT keys.