[Android][Extension] Fixed getCPUInfo algorithm for device capabilities

The original algorithm is not accurate because it ignores the time spent in iowait,
irq and softirq. Now the result is the same as `top` shows.
[Runtime] Move initialization of XWalkRuntimeFeatures

Move this out from XWalkContentBrowserClient::CreateBrowserMainParts()
to a point earlier and more adequated for that initialization.
[Android] Prompt error message when there is filed error in manifest.json.

  When there is field error in the file of manifest.json, error message
should be prompted. This fix is to prompt the error message if there is
filed error in manifest.json. In addition, the corresponding test cases
are added.

BUG=https://crosswalk-project.org/jira/browse/XWALK-648
Application Storage ownership

Application storage should be owned by application system and then it should be given to anyone interested in it (including Application Service).
The benefits:
- those who need storage but do not need service now are able to get it from ApplicationSystem directly
- initialization order of storage and service is easier to handle (now it is being handled from the generic place - ApplicationSystem)
- we're decoupling storage and service and ApplicationService interface can be cleaned from unneeded methods.
Bump version to 4.32.58.0
Merge branch 'master' of github.com:crosswalk-project/crosswalk
Merge pull request #1384 from pozdnyakov/Make_AppSystem_own_AppStorage

Fix Application Storage ownership
Roll chromium-crosswalk to 6d2ee63.

6d2ee63 [SysApps] Make CodecIDToAudioCodec and CodecIDToVideoCodec available as global functions
42904e0 [Android] Use application context for shared pref's creation
7e2e0a5 [Tizen][Android] Add Vibration provider api
7bcdb95 [Android] Use application context for shared pref's creation
e7273a6 [Android] Set webaudio to be muted when volume is set to 0
[Runtime] Implement 'onInstalled' event API.

'onInstalled' event is sent to main page,
1. when the application is first installed.
2. when the application is updated to a new version.
https://crosswalk-project.org/jira/browse/XWALK-723

The PR implements the 'onInstalled' API for the first use case.
Use case 2 isn't implemented at present due to Crosswalk application
update is not supported yet.
[Runtime] Add browsertest for onInstalled event API.
Fix tizen build after efb5f4d14585f59f947790637aed3b57b4c05775 (PR#1384)
Merge pull request #1385 from nagineni/deps_xwalk

Roll chromium-crosswalk to 6d2ee63.
Merge pull request #1386 from pozdnyakov/Fix_tizen_build

Fix tizen build after efb5f4d14585f59f947790637aed3b57b4c05775 (PR#1384)
Merge pull request #1377 from cmarcelo/move-feature-initialization

[Runtime] Move initialization of XWalkRuntimeFeatures
[Tizen] Fix SystemIndicatorWatcher event coordinates according to scale

TizenSystemIndicatorWatcher now is getting the device scale to
recalculate event coordinates.

BUG=https://crosswalk-project.org/jira/browse/XWALK-748
Fix build for G++ 4.8.2 (Fedora 20)

The issue here is that G++ warns about a potential misuse of delete on a
polymorphic object which the base class hasn't a virtual destructor. In
our code that's not a problem because by design, we make the destructor
protected so we can't delete "by the base class pointer type".

However G++ is being picky here, as described in
http://gcc.gnu.org/wiki/VerboseDiagnostics#delete-non-virtual-dtor "the
warning will sometimes be issued for correct code". The workaround of
marking the class final is not widely available yet, so we live with the
simplest fix.
[Tizen] Add Vibration support

This change depends on the VibrationProvider api
which was recently added to chromium upstream. It's not
available in our chromium-crosswalk repo wih 32 rebase so
I have cherry picked those changes into chromium-crosswalk.
Merge pull request #1390 from cmarcelo/unbreak-build-for-fedora-20

Fix build for G++ 4.8.2 (Fedora 20)
[Application][Linux] Convert tools to C++

We don't have strong reasons to keep them a C, so to keep consistency
and make use of our lint checks, moving those to C++.

We still use gdbus here (instead of src/dbus) due to it's convenient
sync API (for the case of the tools, this API is OK) and to avoid
needing to integrate appcore/aul with base::MessageLoop.
Merge pull request #1307 from mrunalk/vibration

[Tizen] Add Vibration support