Fix booting performance issue

Fix booting performance issue

The efl_config is setting device scale information in booting time.
After EFL 1.20 migration, the booting time became longer than before.
It is because The Efl.Ui.Win uses a frame object which is NOT used on Tizen.
Please refer to following stack. The evas_font_load needs around 3 seconds.

  evas_font_load
  _evas_text_font_reload
  efl_text_properties_font_set
  efl_gfx_scale_set
  _edje_text_recalc_apply
  _edje_part_recalc_single_text
  _edje_part_recalc_single
  _edje_part_recalc
  _edje_recalc_do
  _edje_program_run
  _edje_program_run
  _edje_program_run
  _edje_emit_handle
  _edje_message_process
  _edje_object_message_signal_process_do
  _efl_canvas_layout_efl_layout_signal_signal_process
  efl_layout_signal_process
  edje_object_message_signal_process
  _elm_win_frame_style_update
  _elm_win_frame_add
  _efl_win_finalize_internal
  _efl_ui_win_efl_object_finalize
  efl_finalize
  _efl_add_end
  main ()

Setting device scale information does not need to use the frame object.
Moreover Tizen does not use the frame object. So we was about to use Efl.Ui.Win
without the frame object by checking _elm_config->win_no_border.

BUT, we might use Efl.Ui.Win frame object some day.
This patch set is making Efl.Ui.Win keep creating the frame object by checking
ecore_wl2 only (without Efl.Ui.Win).

Change-Id: Ib46fb752e195d41aa0a42169e24e0b5b85b27aa6