The work will proceed in this order:

• Patch the engine build script to separate build for each profile
• Change the embedder code to use different logging methods for different profiles (wearable and TV) as an example
• Create an engine release
• Update the tool code to generate TPKs for different profiles (based on the command line option, the currently connected device, and the definition in tizen-manifest.xml)

flutter-tizen/engine#65 would have to be updated after this is done. Also we will use different rendering backends (evas gl and ecore_wl2) for watch and TV respectively as requested by @xuelian-bai and @haesik.

cc @pkosko (clipboard implementation) @bbrto21 @bwikbs (evas gl contribution)