[DBus] Create DBusManager in ApplicationSystemLinux

ApplicationSystemLinux manages lifecycle of DBusManager and provides
accessor method, so that other parts of the system can use it.
[Applications][Linux] Remove unused variables from xwalkctl
[Applications][Tizen] Fix having to export the HOME variable for user 'app'

When the user changes to the 'app' user (e.g. using 'su - app') the
HOME environment variable is not set by default, this variable is used
for finding the address of the D-Bus session bus.

This is separated in a different header so it can be used by other tools,
see later commits.
[Applications][Linux] Add a tool to launch applications

This tool will launch an Application using its AppID (either via
parameter or via argv[0]).  It will talk to Crosswalk using the
'org.crosswalkproject.Running.Manager' and
org.crosswalkproject.Running.Application' to run and follow the
Application lifetime.

On Tizen, this tool will use the appcode infrastructure to get more
information about the launched application state.

We re-use the functionality of setting the 'HOME' environment
variable that was introduced in the previous commit.

And to avoid polluting the main binary with #ifdef's we put
the platform specific code (dealing with Tizen's appcore) into
a separated header.
[Extensions] Avoid running CrashExtensionTest when --disable-extension-process is set.

Using the ExtensionProcess is mandatory for this test, so we avoid running it.
[Android] Refine the URI scheme Job Factory usage

Mark the Job Factory usage more clearly with three steps:
    1, Add default schemes(http, ftp etc)
    2, Add new basic schemes(data, file, app)
    3, Add scheme interceptors(content, file asset)

Use a custom URLRequestJobFactoryImpl to support navigation
interception and URLRequestJob interception for navigations to
url with unsupported schemes.

Add the request interceptor to handle the shouldInterceptRequest
API for embedder.

BUG=https://crosswalk-project.org/jira/browse/XWALK-655
[SysApps] Add a stub for the Device Capabilities API

This patch adds the basic bits for starting the development of the
Device Capabilties API:

- The IDL files to generate the data serializers.
- The JavaScript shim file, initializing the internal extension system
- An Extension class and an Instance class.
- Register the extension on the XWalkBrowserMainParts (only desktop ATM).
[SysApps] Add an data provider abstraction for the CPU information

The data provider will access the underlying platform and fill a SystemCPU
struct. We are using Chromium classes to retrieve this information, which is
platform independent. In the following patch we will be adding a platform
specialization for querying the CPU load.

Note that the SystemCPU struct is not defined anywhere. By adding SystemCPU dictionary
interface to the IDL file, we instruct the generators to generate the header and
code for this struct, also a function to serialize the struct as a message we can send to
the JavaScript shim.
[SysApps] Add platform dependent CPU info providers

The buildsystem will handle the compilation units accordly to the suffix. No
compile time guards (#ifdefs) are necessary here.

The Windows implementation is just a no-op stub.
[SysApps] Add the Device Capabilities Object

Usually, we could be handling static methods at the Instance object, but this
API requires an EventTarget (coming soon) which adds a bit of complexity,
that's why we need an Device Capabilities Object.

DeviceCapabilitiesInstance has now a BindingObjectStore, which is a class for
keeping track of BindingObjects lifecycle and routing messages. It will
automatically destroy BindingObjects when they are no longer used and route
messages to objects based on the unique ID.

In the JavaScript side we have:

common.BindingObject.call(this, object_id) will initialize the BindingObject
and stablish the "link" for routing the messages.

DeviceCapabilities  is being exported at the root of the API namespace and cannot
be created with "new". We have only on instance of this object per app.
[SysApps] Hook the CPUInfoProvider into SysAppsManager

SysAppsManager will also centralize the creation of data providers. We might
create a new class just for that in the future if there is enough demand.
[SysApps] Implement the Device Capabilities getCPUInfo()

We first add an callback and function to the IDL to make it generate the Promise
reply serializers, which contains the SystemCPU + error message if applicable.

A function handler for "getCPUInfo" is also needed and it will associate the
message coming from the extension with a class method. It is being registered in
the Instance constructor.

GetCPUInfo::Results::Create is generated from the IDL. This function will
create a message which the promise wrapper will receive.

info->PostResult() has internally the callback ID that maps to a callback ID in
the JavaScript shim, so the message will reach the correct recipient.

In the JavaScript shim, is important to use "this_.addMethodWithPromise" so it will
wrap the Binding Object routing ID automatically to the message and associate it
to the Promise.
[SysApps] Add CPUInfoProvider unit tests

The test basically pings each entry point of the API and check if
the returns values are within a sane range.
[SysApps] Add browsertests for DeviceCapabilities getCPUInfo()

Not a replacement for W3C conformance tests, just checking the basic API
functionality and sanity. The test is crafted with the addition of tests
for the rest of the DeviceCapabilities API in mind, that is why we have
a test list with just one test.
Merge pull request #1372 from jeez/fix-crash-test

[Extensions] Avoid running CrashExtensionTest when --disable-extension-p...
Merge pull request #1346 from vcgomes/xwalk-launcher-tool

[Application][Linux] Add a tool to launch applications
Merge pull request #1296 from tmpsantos/devcap_cpu

[SysApps] Implement the Device Capabilities getCPUInfo()
Merge pull request #1187 from alexshalamov/share_dbus_manager

[DBus] Create DBusManager in ApplicationSystemLinux
[Applications][D-Bus] Use versioning in our D-Bus API

Using the recommendations from here [1] to avoid paiting ourselves
into a corner in regard to our D-Bus interfaces, we add versioning
information to our entry points.

[1] http://0pointer.de/blog/projects/versioning-dbus.html
Merge pull request #1368 from vcgomes/xwalk-interface-versioning

[Applications][D-Bus] Add D-Bus API versioning