[UI][Tizen] Create NativeAppWindowTizen

Instead of adding custom behavior into NativeAppWindowViews behind
ifdefs, we create a proper subclass for Tizen. This allow us to
implement observers directly in our window, for example the sensor
observer.

This is a preparation for allowing the window to tell the indicator
which orientation it should paint. In the previous design (using
TizenSensorObserver) we would end up adding more couple (or more layer
of indirection) to accomplish this.

There are some "ifdef" leftovers in NativeAppWindowViews, but can be
moved in later patches.
[Extensions] Reduce boilerplate for external extension tests

Two changes collaborate here to reduce the boilerplate:

- Make a specialized static function to store the external extension
  path for tests, so no reference to a concrete XWalkExtensionService
  is needed.

- Now that we do not need the reference use SetUp() function instead of
  the callback for registering extensions in tests. This change make the
  service passed in that callback unused, we'll remove in the next patch
  to keep this easier to review.

A helper function was added to get the path where an external extension
built for test is.
[Extensions] Remove service parameter from register test callback

XWalkExtensionService allows us to register a function to be called
every time a new XWalkExtensionServer is created, so tests can register
specific extensions. This function may be called multiple times because
we create a (in process) server per Render Process created.

The callback also received a service parameter, to be used for setting
the path for external extensions to be loaded. But the previous commit
changed how tests handle this, so the parameter can be removed.
[Extensions] Add RegisterExtensionForTest() function

This is a small convenience function that reduces the boilerplate when
registering extensions in tests.
[Extensions] Check if reply is valid after a SendSyncMessageToNative

When we try to send a sync message to an extension instance that
became invalid (i.e.: the extension process died) then we might
end up with a NULL reply. We should then check before converting
to a V8Value, thus avoiding the RenderProcess to crash.

That is the same behavior PostMessageCallback has nowadays.
Merge pull request #1101 from cmarcelo/reduce-extension-tests-boilerplate

[Extensions] Reduce extension tests boilerplate
Merge pull request #1102 from cmarcelo/native-app-window-tizen

[UI][Tizen] Create NativeAppWindowTizen
Revert "[UI][Tizen] Create NativeAppWindowTizen"

This reverts commit bd10f497110662662e39e738f91e246d058b5356. It was
still a draft, testing pending.
Merge pull request #1105 from cmarcelo/revert-draft-merge

Revert "[UI][Tizen] Create NativeAppWindowTizen"
Merge pull request #1104 from jeez/extension-module-fix

[Extensions] Check if reply is valid after a SendSyncMessageToNative
Bump version to 3.31.34.0
[SysApps] Add Raw Sockets stub

Just the skeleton to serve as base for the interfaces implementation. No API is
currently exposed.
[SysApps] Add the TCPSocket implementation

This is the initial implementation of the W3C's Raw Sockets TCPSocket interface.
It is not complete but is fully functional. Some issues with the spec are being
worked with the standardization body, like the fact that the send() method is
technically sync (although we implement as async always returning true).

A notable missing feature is the throwing of exceptions on invalid parameters,
but the error callback is still called under these circumstances.

We also add the RawSocketObject class. This class is going to concentrate all
the shared code among the different interfaces of the Raw Socket API. Currently only
the ReadyState is shared.
[SysApps] Make it possible to create a TCPSocket from a connected socket

The TCPServerSocket will need to create a TCPSocket from incoming connections.
This patch makes it possible to create an object in the native side first and
handle the identifier to the JavaScript context.
[SysApps] Add TCPServerSocket implementation

Added an incomplete but functional implementation of the
Raw Sockets TCPServerSocket interface.
[SysApps] Add browser tests for the Raw Socket JavaScript API

Tests if the objects are leaky and if the basic functionality like
send and receive data works. These tests are not API conformance tests.