[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.