QDS need to have the same resource system of QtForMCUs and Qt

QDS always uses the relative path of the asset, which means users cannot put QML into a folder.
something like:

• Root folder
  • assets
    • xxx.png
  • common
    • MyHeader.qml
  • Main.qml

in this case, MyHeader cannot refer to xxx.png like Qt RCC "qrc:/assets/xxx.png" but "../assets/xxx.png", because QDS don't have the concept of the project root folder. 

and QtBridge and QDS have different behaviours of using assets, QtBridge will generate QML into a folder and have its own asserts folder inside... this makes things more complete...
putting assets under "common" is also not a solution because what if have sharing images among folders?
 

the same problem also happens on the QtForMCUs side.

so this means user has to push all (thousands?) QML in the root folder?

on the QtForMCUs side which requires QDS to have more adpation, which is the module system.

1. QDS shall let the user create a module from the QDS IDE (module toolkit)
2. the module information shall read from qmlproject but not qmldir !
   (this means the module shall have the same resource system as the application side)