[Android] Implement the feature of enabling immersive mode for full screen.

Since Android 4.4 (API Level 19) introduces the immersive related mode
for full screen, in Crosswalk, we need to support this feature accordingly.
This PR is resolving this issue by implementing the specific methods
corresponding to the scenarios that full screen mode is turned on and off.

BUG=https://crosswalk-project.org/jira/browse/XWALK-979
Merge pull request #1585 from shawngao5/master

[Android] Fix unable to get the "messaging" permission on Android OS
[Tizen] Check whether app has geolocation permission

This patch adds check whether application has permission to
use geolocation API.
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
Merge pull request #1631 from alexshalamov/check_geolocation_permission

[Tizen] Check whether app has geolocation permission
Do not ignore src/third_party/cros_system_api

This is now a dependency for the Storage Monitor. It may sound like it is
ChromeOS-only dependency, but the Media Transfer Protocol needs a file from it.
DEPS.xwalk: Roll chromium-crosswalk to 655d52b8

655d52b8 Merge pull request #117 from tmpsantos/storage_monitor
0fb3de5 [SysApps] Compile StorageMonitor as a component
[SysApps] Add a data provider for Linux based on Chromium's StorageMonitor

This provider has a big chance of being generic enough to be used for Mac and
Windows. The backend for Android was not implemented yet which makes me sad.

We will have to implement a custom provider for Android (upstream maybe?).
Merge pull request #1633 from tmpsantos/chromium_storage_monitor2

[SysApps] Add a data provider for Linux based on Chromium's StorageMonitor
[SysApps] Use the new DeviceCapabilities implementation

And also enable it by default for Tizen. This new implementation works
for Linux, Windows, Mac and Tizen. Has partial support for Android but
currently is not enabled (since Android uses its own implementation).
Bump version to 5.34.92.0
Merge pull request #1634 from tmpsantos/replace_dev_cap

[SysApps] Use the new DeviceCapabilities implementation
Override notification related interface from content

There are four methods in content browser client which are for
client to implement to support web notification.
Override those apis with empty function bodies first.
[Android] Implement W3C WebNotification API

W3C web notification API is defined at http://www.w3.org/TR/notifications/.
On Android, web notifications are well matched to system notifications.
To invoke js callbacks when system notification got clicked or canceled,
two pendingIntents are binded to the notification.
Since Android only keeps one pendingIntent for specified Context/Class/Category,
the unique id of the notification is used as the Category of the pendingIntents.

Platforms other than Android keeps empty implementaion for notification related
interfaces.

TEST=XWalkCoreTest org.xwalk.core.xwview.test.WebNotificationTest
BUG=https://crosswalk-project.org/jira/browse/XWALK-94
[Runtime] Should provide the application id exactly the same as the
installed one.

Current logic in Update() only check whether the provided id is not
empty, so change it to check if the expecting application id is the same
as the installed one.
Merge pull request #1626 from ShDavidliu/Immersive

[Android] Implement the feature of enabling immersive mode for full scre...
[Runtime] Enable to update an XPK/WGT package in service mode.

When running xwalk under service mode, the updating function should take
place when installing an installed application, the same behavior as
single application mode.
[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.
Merge pull request #1593 from shaochangbin/wgt-manifest

[Runtime] Separate WGT applications manifest handling from XPK applications.