[Android] Add reload getTitle clearHistory in XWalkView for internal use
- Load: reload
- UI: getTitle
- Navigation: clearHistory
- Add stop, reload buttons in XWalkViewShellActivity
- Add testcase for reload, clearHistory
[Android] Add the test case about setDatabaseEnabled

Test database by set the function setDatabaseEnabled true or false.
Then get the result by load the html which check the database
enabled or not.

This test case should add the parameter "--test_data", as follows:
build/android/run_instrumentation_tests.py --test-apk XWalkCoreTest \
--test_data xwalkview:xwalk/test/data/device_files/ \
--verbose -I --num_retries=1 -f testDatabaseEnabled
[Android] Specify version code/name for android outputs at gyp time

The version in AndroidManifest.xml has two parts:versionCode and versionName.
VersionCode is an increasing integer to identifing upgrade.
VersionName is a human readable string.

For xwalk, VERSION file should be the only place to maintain version.
So this patch removes the hard coding in AndroidManifest.xml.

Insteadly, version code and version name will be specified as parameters at
gyp time for android's ant action.

For versionCode, it's calculated through version.
The formula is:
versionCode = shift +
              patch * 10 +
              build * 1000 +
              (major+minor) * 100000
Shift is the configuration bit. Currently, 1 for x86, 2 for armv7 and 3 for arm.
[Android] Disabled the testNormalUrl temporarily.

Since the device issue, it can not access the network,
so disabled testNormalUrl temporarily.
It will be enabled later.
[Android] Fix the invalid arguments issue in XWalkRuntimeClient.onActivityResult.

Missing the instance argument in onActivityResult, this causes exception while
onActivityResult is called.

BUG=https://github.com/crosswalk-project/crosswalk/issues/732
Merge pull request #728 from yongsheng/permissions

[Android] Don't add permissions for runtime library
Merge pull request #704 from wang16/gyp_android

[Android] Specify version code/name for android outputs at gyp time
Merge pull request #729 from wuhengzhi/disableNormalUrl

[Android] Disabled the testNormalUrl temporarily.
Merge pull request #733 from sqliu/otcshare-hotfix-onActivityResult

[Android] Fix the invalid arguments issue in XWalkRuntimeClient.onActivi...
Bump version to 1.29.6.0
Merge pull request #615 from kurli/api

[Android] Add reload getTitle clearHistory in XWalkView for internal use
Merge pull request #560 from wuhengzhi/master

[Android] Add the test case about setDatabaseEnabled
[Android] Implement APIs for external extensions

Similar to native extensions system, we need to allow web developers
or others to write their own extensions. Due to the shared mode, there
are some client classes in runtime client side which are used by
external extensions.

1. XWalkExtensionClient: the base class for external extensions.
2. XWalkExtensionContextClient: the context to be used by extensions to
help get the context.
3. Configuration system: define a configuration system to specify what
kind of extensions to be loaded and created by crosswalk.

So for web developers, an external extension is implemented with below steps:
1. Write the JavaScript code stub same as the native extension system.
2. A new class inherited from XWalkExtensionClient implements the methods
used by JavaScript.
3. Configure the extension in extensions-config.json which should be packaged
in android asset, like:
[
 {
   "name": "myextension",
   "class": "com.example.MyExtension",
   "js_api": "myextension.js"
 }
}

Developers don't have to create and register their extensions. Instead,
crosswalk runtime will load and create them according to the configuration
system.

Next is to add one test case for external extension mechanism.