Enable Aura XWalk build by default

Enabled Aura by default for XWalk Linux and Windows builds, also enabled window frame and window header for XWalk Aura windows on Linux desktop.

The NativeAppWindowViews::CreateNonClientFrameView is now overridden only for Windows in order to make visible Aura window frame&header on Linux desktop (NativeAppWindowViews::CreateNonClientFrameView had been overridden to show OS window decoration instead chrome-style UI, however the used views::NativeFrameView works only on Windows).
[Runtime] Change the runtime database backend to sqlite

Using Sqlite database instead of JSON format database, it will guarantee
data security and data integrity.

The source code is refered to the file sqlite_server_bound_cert_store.cc in
Chromium for the usages of sql::Connection.

The applications information will migrate from JSON DB to the new SQLite
DB automatically.

In Tizen package info installer, change the owner of SQLite DB files to "app" user,
since these files will access by "app" user when launch from home screen.

After bumped to Chromium 31, when compeling the xwalk with this patch, in
application_protocols.cc, there should be an error said: invalid use of
incomplete type ‘struct base::SequencedWorkerPool’, add the header file will
solve this issue.
[Runtime] Clean the JSON format applications database source code

The JSON format DB will not be used anymore, using SQLite DB instead, so
remove those excess code.
Merge pull request #866 from tmpsantos/function_handler

[Extensions] Refactoring of the XWalkExtensionFunctionHandler
Merge pull request #838 from pozdnyakov/Aura_by_default

Enable Aura build by default
Merge pull request #801 from takethathe/sqlite

[Runtime] Change the runtime database backend to sqlite
[Extensions] Keep the IDL file close to the implementation

Teach the build system to process every file in the source section
ending with .idl. Now the .idl files can stay in the same directory
as the implementation making it more self contained.
[Extensions] Move extensions tests to the new IDL rule

The buildsystem now supports processing of .idl on the source
section, there is no need to include the IDL processor again
for the browser tests.
[Dialog] Use a more descriptive name for parameters

We have no plans to generate the JS shim in a short term, so use a more
verbose description of the parameters matching the IDL.