[Extensions] Change when we create the extensions

This patch changes slightly when we create the extensions, instead of
calling XWalkExtensionService::OnRenderProcessHostCreated() and waiting
for the delegate functions to be called, the interface now expects
vectors to be passed with the extensions.

There are three upsides:

- At extension creation time we have the reference to RenderProcessHost,
  allowing us to pass that to the extensions (and in the future pass the
  Application, which will have 1-1 relationship with RPH).

- We don't need to expose the XWalkExtensionServer. A full object
  interface was being included and passed around, just for using one
  function. Exposing less objects gives us more freedom to change things
  in the future.

- We simplify the usage of XWalkExtensionService, by removing the use of
  Delegate for creating the extensions.

There are two downsides, which I consider minor compared to the
benefits:

- It's not clear in the type that ownership is being passed to
  XWalkExtensionService. It is documented and we can add a more clear
  type in the future. For now we can live with this.

- We don't have the information whether the extension was registered
  successfully or not from the tests. However, other later assertions
  assured that the test passed.

The patch is quite big because we changed all the plumbing in the tests.
[Extensions] Build fix

Fixes linking errors when building with component=shared_library.

undefined reference to 'WebKit::WebScopedMicrotaskSuppression::initialize()'
undefined reference to 'WebKit::WebFrame::frameForCurrentContext()'
undefined reference to 'WebKit::WebScopedMicrotaskSuppression::reset()'
undefined reference to 'WebKit::failedAssertion(char const*, int, char const*, char const*)'
undefined reference to 'AnnotateHappensAfter'
undefined reference to 'AnnotateHappensBefore'
undefined reference to 'AnnotateHappensAfter'
Merge pull request #1341 from tmpsantos/xesh_build_fix

[Extensions] Build fix
Fix warnings in Tizen build

Tizen uses an old G++ version, but doesn't hurt keeping its build
warning free when possible.

Three cases of initialization list ordering mismatch and one case of G++
considering taking 0 as a signed literal and concern about comparing
unsigned (size_t) with signed (the literal).
Make the Tizen indicator take the current Display configuration

The Display knows about device scale as well as current orientation.
This avoid passing specific or invalid orientation information

Also do not create a watcher before valid display information is set.

When xwalk is launched in landscape mode, it now has the right
indicator size.
Merge pull request #1343 from kenchris/display

Make the Tizen indicator take the current Display configuration
Merge pull request #1342 from cmarcelo/fix-tizen-warnings

Fix warnings in Tizen build
Merge pull request #1336 from cmarcelo/pass-extensions-instead-of-registering

[Extensions] Change when we create the extensions
[Extensions] Fix Android build
Merge pull request #1344 from cmarcelo/fix-android

[Extensions] Fix Android build
Fix the touch area and indicator size after rotation change
Merge pull request #1345 from kenchris/fixtouch

Fix the touch area and indicator size after rotation change
Fix more warnings for Tizen

Initialization order complaints from G++ 4.5.
Merge pull request #1348 from cmarcelo/fix-tizen-warnings-2

Fix more warnings for Tizen
Bump version to 3.32.56.0
[Runtime] Register system events information into database during installation.

As is mentioned in https://crosswalk-project.org/jira/browse/XWALK-519,
this PR registers system events at application install time. In detail,
after installation of application pacakge is completed, the main
document will be executed to register the events into system database.