Implement `Tizen Core` embedder

[JSUYA]

Currently, our embedder is built on EFL's ecore, ecore_imf, ecore_input, ecore_wl2, eina, and eldbus libraries.
(Dependencies on evas and elm have already been removed.)

The EFL library was deprecated in Tizen 10.0, and according to Tizen policy, its API will be removed +2 version later.
(https://review.tizen.org/gerrit/c/platform/upstream/efl/+/321724)
(https://review.tizen.org/gerrit/c/platform/upstream/efl/+/321255)
(https://review.tizen.org/gerrit/c/platform/upstream/efl/+/324645)

Tizen will transition from EFL's ecore to TizenCore (tcore).
https://docs.tizen.org/application/native/guides/applications/tizen-core/tizen-core/

Therefore, a separate embedder that implements code currently written in ecore and ecore_imf in tcore must be prepared.
(This change will apply to the common profile first, and the TV profile is not yet planned.)

Action Items

• eldbus will be replaced to gdbus. - Replace eldbus with gdbus #148
• eina will be replaced to std::vector (maybe?)
• ecore api will replaced to tcore
• ecore_wl2 api will replaced to tcore_wayland
• ecore used in plugins will be replaced with tcore.
• Below target plugins will add tcore-based C++ implementations:
  flutter-tizen/plugins/audioplayers
  flutter-tizen/plugins/geolocator
  flutter-tizen/plugins/image_picker
  flutter-tizen/plugins/permission_handler
  flutter-tizen/plugins/tizen_app_manager
  flutter-tizen/plugins/tizen_package_manager
  flutter-tizen/plugins/tizen_window_manager
  flutter-tizen/plugins/video_player - [video_player] Replace ecore with tcore plugins#958
  flutter-tizen/plugins/video_player_avplay - [video_player_avplay] Replace ecore with tcore plugins#960
  flutter-tizen/plugins/video_player_videohole - [video_player_videohole] Replace ecore with tcore plugins#959
  flutter-tizen/plugins/wakelock_plus
  flutter-tizen/plugins/webview_flutter_lwe

[JSUYA]

I've uploaded PoC commit for tizen-core-wl to our internal git (f-project/embedder).
I'd like to share some additional work items identified during this process.

• devel-api of the dali package, used to implement the NUIFlutterView, has been separated into the integration-devel rpm in Tizen 11. Therefore, sysroots for Tizen 11 and later may require separate configuration.
• TizenEventLoop, implemented using Ecore_Pipe, may need to be implemented using std::thread. (like this Replace Ecore Queue with Message Loop #155)
• tizen-core-wl and tizen-core-imf are under development, so their interfaces may change continuously. (Recently, init/shutdown API changes)
• tizen-core-imf's init function is not functioning properly (tcore module.so not found).

+) I'm also considering implementing it using wayland/glib. This is because splitting libflutter_tizen.so(for tcore) will cause app compatibility issues. I tried to implement wayland/glib-based PoC, but it caused frame drops when moving cursor, and I haven't been able to resolve this yet. I'll revisit this issue later.

[xiaowei-guan]

TizenEventLoop, implemented using Ecore_Pipe, may need to be implemented using std::thread.
==》If I remember correctly, EventLoop is responsible for executing Flutter tasks on platform thread. I think we don't need create a new thread.
==>The reason vsync waiter creates a new thread is that the tdm_vblank function blocks the platform thread.