[Runtime] Add XPK package generate tool

The python script can generate XPK package from Crosswalk application
resources, furthermore, it will generate a RSA private key if it's invalid.
[Tizen] Polish Python code according to Chromium Python style guidelines.

Per Chromium Python style guidelines,
http://www.chromium.org/chromium-os/python-style-guidelines
This CL sets single quote for string values, and sets functions names
with CapWords() style.
[Tizen] Enable pkginfo uninstall for Tizen.

This CL supports to uninstall package information from Tizen Database,
as well as remove application icons, execute path and XML file from Tizen system.

As for the python script arguments, the --install option will not take
values any more, also a new option --uninstall is added to support
uninstall package information from Tizen.

For class InstallHelper() in Python, the parameter input_path is removed from
constructor, because it could be generated by the other parameters.
Also several class member variables are added, e.g, icon_path_ , execute_path_,
which could be shared by install and uninstall functions.

Besides, we found the issue that application icon could not display on home
screen if package name contains white spaces. To fix this issue, the installer
script strips these whitespaces when writing package information into database.
Merge pull request #665 from shaochangbin/cb-uninstall

[Tizen] Enable pkginfo uninstall for Tizen.
Merge pull request #669 from takethathe/generator

[Runtime] Add XPK package generate tool
Separate Client<->Server messages from regular Extension messages

IPC has a way to identify the messages by "class", based on the MsgStart
identifier, by using the IPC_MESSAGE_CLASS() macro. This will make
filtering of messages for client<->server interface easier.
Make extension instances run in a single shared thread

This is a change on the execution model of the extensions. The code for
each instance used to run in its own thread. In the Browser Process, for
in-process extensions, they'll run in a dedicated extension thread. In
the Extension Process, they'll run on the main thread. Of course,
extensions still have the freedom to create their own threads.

Two main reasons for changing execution model are:

(a) In practice our use cases for external extensions, instances needed
to interact with glib-based libraries, and all the callbacks ended up
going back to the main thread. We were not collecting much benefit of
implicitly creating threads.

(b) Sharing data between instances now will be easier, since it won't
imply sharing data between multiple threads. One common problem is that
when writing instances, the jump from "simple case" to "multithread
bugs" was too small. It was too easy to face race conditions without
being aware of them.

One notable change is that we stop using XWalkExtensionRunner
abstraction. Now that we have an object dedicated to manage the
instances (XWalkExtensionServer) we don't really gain much from the
indirection -- as can be seen in the patch diff.
Remove XWalkExtensionRunner abstraction

We don't use this anymore. It made sense back in time when there were
not a specialized object to handle instances (we now have
XWalkExtensionServer) and when there was complex logic involved in
running each instance in a separated thread.