[Ozone Wayland] Fix for evasgl issue/crash in efl_webview_app/mini_browser on Note4

[Ozone Wayland] Fix for evasgl issue/crash in efl_webview_app/mini_browser on Note4

Below evasl gl errors are seen when we run efl_webview_app/mini_browser on Note4:
ERR<5058>:EvasGL modules/evas/engines/gl_common/evas_gl_api_ext.c:327 evgl_api_ext_init()
glGetString returned NULL! Something is very wrong...
ERR<5058>:EvasGL modules/evas/engines/gl_common/evas_gl_core.c:1437
evgl_engine_init() Extensions failed to load. This shouldn't happen, Evas GL load fails.
ERR<5058>:evas_main lib/evas/canvas/evas_gl.c:367 evas_gl_context_version_create() Failed
creating a context from the engine.
[0518/235828:FATAL:gl_shared_context_efl.cc(33)] GLSharedContextEflPrivate(): Create evas
gl context Fail

However, these errors are not seen for ubrowser.

On Note4, tt seems like all gl/egl initialization must be completed
before the evas_object is created and its evas canvas is used to
created an Evas GL object. Platform team may explain more on this.

In chromium-efl, this initialization is done in the ewk_context_default_get() call.
In case of efl_webview_app/mini_browser, ewk_context_default_get() call is made after the
main window gets created whereas its called before main window creation for ubrowser.

Bug: http://web.sec.samsung.net/bugzilla/show_bug.cgi?id=12492
Reviewed by: DaeHyun Ko, Siba Samal

Change-Id: Iceec7d29c7057cd00d62453c2fd753b876c096cd
Signed-off-by: Chandan Padhi <c.padhi@samsung.com>