[SysApps][Android] Refine display attributes based on latest spec

SPEC=http://www.w3.org/2012/sysapps/device-capabilities/
BUG=XWALK-1309
Merge pull request #1773 from halton/display_refine

[SysApps][Android] Refine display attributes based on latest spec
[Application][Extension][Runtime] Merge xwalk-launcher with extension process in service mode

With this update when running in service mode, XWalkExtensionProcess will be
bootstrapped by launcher instead of runtime daemon.

This improvement has several advantages:
1. Some Tizen Device APIs binding with AUL can be directly called in launcher,
instead of passing request through IPC.
2. Less process number for an application, the system footprint will be smaller.

Implementation details:
Once a XWalkExtensionProcessHost is created, it will notify corresponding running
application's DBus object to send a signal to its launcher. Then launcher will
retrieve the created IPC channel and instantiate a XWalkExtensionProcess.
Merge pull request #1725 from seanlong/ep2launcher

[Application][Runtime][Extension] Merge xwalk-launcher with extension process for service mode
[Tizen] packaging: Remove dead %patch calls.

We don't care about Tizen 2 anymore, and the referenced files do not even
exist anymore.
Merge pull request #1802 from rakuco/remove-tizen2-remains

[Tizen] packaging: Remove dead %patch calls.
Move to Chromium 35.0.1916.17.

This is another one of those big commits made of a lot of smaller squashed
commits done in our "next branch".

Some of our tests are broken but pass in Release mode; we are working on
fixing them.

Most of the changes in the code are caused by upstream Chromium changes,
namely:

* https://codereview.chromium.org/109013004
* https://codereview.chromium.org/120303003
* https://codereview.chromium.org/126763003
* https://codereview.chromium.org/135013008
* https://codereview.chromium.org/154473002
* https://codereview.chromium.org/159173002
* https://codereview.chromium.org/161113002
* https://codereview.chromium.org/165893002
* https://codereview.chromium.org/172163003
* https://codereview.chromium.org/177863002
* https://codereview.chromium.org/183743021
* https://codereview.chromium.org/183853011
* https://codereview.chromium.org/184563006
* https://codereview.chromium.org/185713008
* https://codereview.chromium.org/185863003
* https://codereview.chromium.org/186883002
* https://codereview.chromium.org/187223003
* https://codereview.chromium.org/187223003
* https://codereview.chromium.org/189333004
* https://codereview.chromium.org/190663012
* https://codereview.chromium.org/190663012
* https://codereview.chromium.org/190853004
* https://codereview.chromium.org/191093002
* https://codereview.chromium.org/196073002
* https://codereview.chromium.org/196413016
* https://codereview.chromium.org/198333004
* https://codereview.chromium.org/199063003
* https://codereview.chromium.org/206713004
* https://codereview.chromium.org/207353003

Additionally, the following commmits are worth mentioning:

  M35 gardening: stop passing --fatal-warnings to ld on Tizen Common.
  XWALK-1379 is tracking this. There are linkage failures because of
  sqlite3 symbols used by libpkgmgr-info.so and libpkgmgr_parser.so.

  [Tizen] Remove Mesa patch that's not needed anymore.
  This was fixed differently upstream with r255915 in Chromium.

  Sync gyp_xwalk with upstream gyp_chromium
  Synced to revision r258119.

  [Android] Fix core shell crash issue after rebasing to Chromium35
  icu_use_data_file_flag has been enabled on Android after Chromium35.
  Need to package icudtl.dat resource.
  TODO:
  1. It will also be crashed on Shared mode, caused by application context issue.
  2. CoreShell will be crashed when exit. Will track with XWALK-1366.
Merge pull request #1798 from rakuco/xwalk-m35

Move to Chromium 35.0.1916.17.
make_apkg.py: Catch library and version errors

When creating (x86/ARM) packages, emit a warning if the
corresponding architecture libxwalkcore.so is not found.
If no packages have been created due to missing
libxwalkcore.so, abort with an error message.

Also, check if values <=0 are passed to --app-versionCode or
--app-versionCodeBase, and abort with an error message in case.