[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.
Refine some public files in xwalk runtime.

The public files under xwalk/runtime/browser should be
located to the correct compiling path and the unused codes
related to Android port in the resource dispatcher host
delegation file should be removed. This fix is to refine
the corresponding files in xwalk runtime.

BUG=https://crosswalk-project.org/jira/browse/XWALK-620
[Runtime] Polish a Sqlite table selection statement.

The name 'registered_event' is not explictly declaired which table it
comes from in previous SQL statement.
This PR explictly clarifies column of which table is selected.
[Tizen] Remove legacy install_into_pkginfo_db.py from RPM

This file is not used anymore.
[Android][SysApss] Fixed getMemoryInfo to support Android 4.0 and below.

1. The original implementation uses an API avaible since API level 16. Change
the implementation to reading file "/proc/meminfo" when the target system
is Android 4.0 and below.
2. The spec http://device-capabilities.sysapps.org/#memory requires to return
byte instead of KB. So change the unit to byte.
[Android] Fix app will crash at exit if runtime lib not found

It's because, the code is trying to get a boolean value from
method onKepUp in runtime. It will return null if runtime lib
not found.
For other class like String, return null is OK. But for boolean,
java will try to turn Boolean object null into boolean, which
causes NullPointerException.

BUG=https://crosswalk-project.org/jira/browse/XWALK-627
Merge pull request #1240 from itlodge/fix_memory

[Android][Extension] Fixed getMemoryInfo to support Android 4.0 and belo...
Merge pull request #1244 from ShDavidliu/resource_dispatcher

Refine some public files in xwalk runtime.
Roll chromium to aac7580

Bring in 4 commits:
d51e985 [Tizen] Dynamically load the camera driver at runtime
c1b54ed [Tizen] Add the EGL backend in VAVDA for Tizen Mobile.
55288b3 Revert "x11: Fix a few touch-event related issues:"
1127c91 [Tizen][Performance] Enable Accelerated 2D Canvas.
[Extensions] Make it possible to export a custom object

Currently the JavaScript shim receives an "export" object which you are supposed
to add properties. But what if you want to export an object created in the shim
instead? This patch adds support for that: now, by assigning it to an object,
the object gets exported at the root of the API namespace instead of the
"export" object.
[Extensions] Add tests for exporting objects in the JavaScript shim

The test verifies if both methods of exporting objects (hanging properties
on the "export" object or assigning it to another object) are working fine.
Merge pull request #1246 from shaochangbin/sql

[Runtime] Polish a Sqlite table selection statement.
[Tizen] Implement geolocation adaptation for Tizen

To provide full geolocation functionality, two things need to be implemented.
1. LocationProviderTizen which is a realization of LocationProvider interface.
2. Geolocation security request should be handled and security dialog should be
shown to the user.

This patch provides implementation for [1]. Security dialog handling
would be submitted in a separate patch.
Fix occurences of "CrossWalk" in the Android port.

The name of the project is "crosswalk" not "CrossWalk".
Merge pull request #1254 from jchen10/camera_dlopen

Roll chromium to aac7580
Merge pull request #1237 from tmpsantos/export_object

[Extensions] Make it possible to export a custom object
Merge pull request #1249 from jeez/remove-legacy

[Tizen] Remove legacy install_into_pkginfo_db.py from RPM
Merge pull request #1247 from alexshalamov/geolocation_tizen

[Tizen] Implement geolocation adaptation for Tizen
[Tizen] Fix build regression caused by PR #1249

Legacy install_into_pkginfo_db.py related things are not removed
cleanly by PR #1249, it cause the rpmbuild failure.
[application] Remove "application launch from local path" support

We rely fully on main document as application entry point (see
http://anssiko.github.io/runtime/app-lifecycle.html).

The deprecated "application launch from local path" code path support should be removed as
1) it is not used but brings extra complexity
2) it does not provide the logic which we rely on in many places within xwalk (for instance initialization of main_runtime_ or non-persistent main document implementation).