[Tizen/Desktop] Prepare app installation code for using from xwalkctl

SSIA. Application storage and installer were moved to the 'common' folder,
'xwalk_application_common.gypi' was created to be further used by xwalkctl.
Besides, this patch removes the unused "db_store" code.
Merge pull request #2125 from pozdnyakov/app_installation

[Tizen/Desktop] Prepare app installation code for using from xwalkctl
Add Multiuser support on Tizen by removing hard coded path.

This change need to use the lib libtzplatform-config.

Change-Id: Iedb7ad89e9e8dbc0d9dcf2e3473c1c359fd2704b
Signed-off-by: Stephen Clymans <stephen.clymans@open.eurogiciel.org>
Merge pull request #2120 from eurogiciel-oss/Add_Tizen_Multiuser

Add Multiuser support on Tizen by removing hard coded path.
Bump version to 8.36.160.0
[Android Extension] Fix Activity leaking caused by DeviceCapabilities extension

The static XWalkMediaCodec singleton instance indirectly holds a
reference to Activity via XWalkExtensionManager, it would prevent the
Activity object from GCed and then leak it and all its resources.

BUG=https://crosswalk-project.org/jira/browse/XWALK-2000
[Android] Add a tracing tool for XWalk

It's a wrapper of adb_profile_chrome.py from upstream to support tracing in XWalkRuntimeClientEmbeddedShell.

BUG=XWALK-1977
Merge pull request #2128 from hmin/activity-leak

[Android Extension] Fix Activity leaking caused by DeviceCapabilities ex...
Merge pull request #2126 from kurli/profile

[Android] Add a tracing tool for XWalk
[Android] Refine the key event dispatch for xwalkview

Including following changes:
1. Hook shouldOverrideKeyEvent and onUnhandledKeyEvent into
   content layer correctly.
2. Move the key event handling in xwalkview into dispatchKeyEvent.

After change the process of key dispatch in xwalkview will be:
  Activity.dispatchKeyEvent
  -> XWalkClient.shouldOverrideKeyevent
        <if shouldOverrideKeyevent returns true>
     -> XWalkView.dispatchKeyEvent (handles backkey here)
        <if shouldOverrideKeyevent returns false>
     -> dispatch keyevent to renderer
        <if renderer doesn't consume the keyevent>
        -> web_contents_delegate::HandleKeyboardEvent
           -> XWalkWebContentDelegate.handleKeyboardEvent
              -> XWalkClient.onUnhandledKeyevent

It's pre-adjust for Embedding API v2.

Related to bug: XWALK-2003
[Android] Mark content as a local scheme in blink

Now there is no option to enable the cross-origin-access in the
context of content url in embedded mode. Regarding file scheme we
use setAllowUniversalAccessFromFileURLs option to support the
cross-orign-access. This way works for all the schemes which are
recognized as the "local" ones in blink. That's straightforward
to let content scheme follow this way to support the
cross-orgin-access setting.

BUG=XWALK-1959
Merge pull request #2130 from xingnan/1959

[Android] Mark content as a local scheme in blink
Merge pull request #2129 from wang16/keydispatch_api

[Android] Refine the key event dispatch for xwalkview
[Tizen/Desktop] Re-organize storage partition management

This patch removes storage partition cleanup logic from Application
Storage and Package Installer making them completely independent
from browser content API layer. Hence now both of them can be used
outside the browser process (e.g. from 'xwalkctl').

The Application Storage implementation is now much simpler which is
very important as we have plans to create an alternative Application
Storage implementation for Tizen, based on the platform 'app_info.db'.
Bump version to 8.36.161.0
[Android] Adjust annotation of Embedding API for documentation

Before reflection layer for shared mode lands, there are still
public methods in org.xwalk.core which are not supposed to be
Embedding API. So we still need to support doclava for now.

This commit includes following changes:
1, Reorder the declare sequence to make Exposed APIs prior to the
internal one with the same function name (which takes internal
class as paramter).
2. Add @since tag for all APIs, although since tag is not supported
in doclava, it's still worth to do it for API maintenance. This
also applies to the internal classes, before in future, the annotation
in org.xwalk.core will be generated from org.xwalk.core.internal by
script. So for now, we need to keep them synced.
3. Add @hide to the non-Embedding API public methods.

Related Bugs: XWALK-1856, XWALK-2017
[Android] Hook the native destroying of XWalkview into GC

Now we need to restrict users to explictly call the onDestroy method
of XWalkView to make sure the native part of XWalkView will be
destroyed. The patch leverages the solution in Chromium and remove
the restriction.

BUG=XWALK-2010
Merge pull request #2137 from xingnan/2010

[Android] Hook the native destroying of XWalkview into GC
Merge pull request #2138 from wang16/api_doc

[Android] Adjust annotation of Embedding API for documentation
Merge pull request #2136 from pozdnyakov/storage_partitions

[Tizen/Desktop] Re-organize storage partition management