[Tizen] Check whether app has geolocation permission

This patch adds check whether application has permission to
use geolocation API.
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
[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.