[Android] User TextureView as the default rendering backend view.

There are several issues with SurfaceView rendering backend, including:
(1) Can't be animated/transformed/translucent.
(2) Multiple SurfaceView overlapped in the same ViewGroup will cause undefined behavior.

Those are not issues for Chrome for Android, since Chrome for Android uses only
one SurfaceView and everything is painted/compsited inside the SurfaceView.
But for Crosswalk, we may have multiple SurfaceViews for each embedding App, so the
drawbacks of SurfaceView may cause some bugs.

This CL makes TextureView as the default rendering backend, which can overcome the
drawbacks of SurfaceView. Eventhough the TextureView increase more memory usage.

To switch back to SurfaceView,set the ANIMATABLE_XWALK_VIEW preference value to be
false before using XWalkView.

BUG=
Revert "[Android] Multiple profile support"
Merge pull request #2417 from crosswalk-project/revert-2401-profile

Revert "[Android] Multiple profile support"
Bump version to 9.38.205.0
Merge pull request #2389 from crosswalk-project/use-texture-view-by-default

[Android] User TextureView as the default rendering backend view.
[Tizen] Check signature value using xmlsec1 library

Based on API provided by xmlsec1 library, signature value and reference
are checked.