[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.
[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.
Merge pull request #1636 from takethathe/update_check

[Runtime] Should provide the application id exactly the same as the installed one.
Merge pull request #1635 from takethathe/service_update

[Runtime] Enable to update an XPK/WGT package in service mode.
Merge pull request #1470 from wang16/w3c_notification

[Android] Implement W3C notification API
Revert "[Android] Add eclipse build support for xwalk_core_library"

This reverts commit 3f155dfc89e39dbde7adeecd4a1fa139fec88789.
Revert "[Android] Fix incorrect res ids for apps using cordova xwalk"

This reverts commit a2ece240670d66509f3b4eafa55ced7172f0f23f.
[Android] Determine id for resources in chromium at runtime

In chromium, there are two java target contains resources.
They are org.chromium.content.R and org.chromium.ui.R. The
R.java of these two package in chromium repo are just a
declaration with no ids specified.

In chromium's gyp system, it is handled well to make sure the
ids are unique for each resource.

If xwalk core is used as an Android library project. All the
resources will be only counted in org.xwalk.core.R. Previously,
we added an additional step running as pre-compile to copy
org.xwalk.core.R to org.chromium.content and org.chromium.ui to
make the ids correct.

Now we want to expose a set of embedding API based on xwalk core
library, which will be an Android library project used by multiple
projects. The original way is not appropriate any more.

The new solution is to set the ids at runtime by using java
reflection to iterate over chromium resources.

BUG=https://crosswalk-project.org/jira/browse/XWALK-1042
[Android] Clean everything in xwalk_core_library folder for each build

Otherwise, there may remain some legacy files even it's removed
from the source tree.