[Android] Add the check of application launch path in packaging tool.

   Since there is no prompt when there is no application launch path
in the manifest.json file, to improve the user experience of crosswalk,
in the packaging tool, add the check of application launch path in packaging
tool. The related test case is added.

BUG=https://crosswalk-project.org/jira/browse/XWALK-645
[Android] Update the user interface of http authentication dialog.

  Update the text margin and the string of http authentication dialog.

BUG=https://crosswalk-project.org/jira/browse/XWALK-646
[Android][SysApps] Change the unit of storage capacity to byte.

According to the spec
http://device-capabilities.sysapps.org/#systemstorage-interface ,
the ``capacity`` should be in bytes but the original implementation
is in kilobytes.
Merge pull request #1290 from ShDavidliu/packaging_manifest

[Android] Add the check of application launch path in packaging tool.
Merge pull request #1299 from ShDavidliu/ui_http_auth

[Android] Update the user interface of http authentication dialog.
Merge pull request #1322 from itlodge/fix_storage_unit

[Android][SysApps] Change the unit of storage capacity to byte.
[Tizen][Temp] Enforce device scale factor value to '2.0' on Tizen

Enforce device scale factor value to '2.0' on Tizen so that viewport meta tag works properly on Tizen devices.
This is a workaround until Chromium r235967 is not within chromium-crosswalk code base.
Bump chromium-crosswalk in DEPS.xwalk
Merge pull request #1325 from pozdnyakov/Force_Device_Scale

[Tizen][Temp] Enforce device scale factor value to '2.0' on Tizen
Merge pull request #1321 from junmin-zhu/default

[Android] Enable the embedded mode by default for packaging tool
[Tizen] Indicator: Close FD after destruction of watcher
Merge pull request #1328 from kenchris/fd

[Tizen] Indicator: Close FD after destruction of watcher
[Extensions] Invalidate exposed functions when the extension module is destroyed

The crash identified back when doing our Chromium update could not be
reproduced. This commit also adds a test. Without the change, RP would
crash in the test. With the change, RP doesn't crash anymore.

TEST=XWalkExtensionsIFrameTest.KeepingReferenceToFunctionFromDestroyedIFrame
BUG=https://crosswalk-project.org/jira/browse/XWALK-184
[Tizen] Update TizenSystemIndicator Plug Operations

This new operation codes were added from tizen_2.1/20130514.052329
Merge pull request #1331 from ricardotk/indicator2

[Tizen] Update TizenSystemIndicator Plug Operations
Merge pull request #1326 from alexshalamov/bump_deps_xwalk

Bump chromium-crosswalk in DEPS.xwalk
Merge pull request #1329 from cmarcelo/fix-xwalk-184

[Extensions] Invalidate exposed functions when the extension module is destroyed
Bump version to 3.32.54.0
[Extensions] Move kXWalkExternalExtensionsPath to extension switches

So that both xwalk_runtime and xesh (the test shell for extensions) can
use it. This prepares to make xesh build do not depend on the rest of
the runtime.

I was avoiding moving this constant here because it was not necessary
for extension system. But given the multiple users, I consider extension
itself a fair place to store this constant.
[Extensions] Make xesh depend only on what it uses

Currently xesh (XWalk extension test shell) depends on the entire
xwalk_runtime target. This is not needed, since the shell was designed
to use only Extension system.

One drawback of the current approach is that unrelated changes end up
forcing a recompilation of xesh, this have some impact when running
ninja without target parameters.

Instead of depending on the xwalk_runtime target, this patch makes xesh
depend directly on the base libraries and include the sources from
extensions.gypi.

This could be further improved by making extension system itself into a
static library, used both by xwalk_runtime and xesh. This would avoid
compiling the extension system files for each target.