Collect property sheets in the updater

Parse specifics files from modules.

For now we skipped parsing the specifics files from the modules. (designer folder in the same location as qmldir file).

We identified use cases for the effect maker that require those.

There is the question of precedence. specifics files in Qt Design Studio should have precedence over specific files inside the module. Midterm we want to remove all specifics from Qt and move them to Qt Design Studio. Another option is to parse specifics only inside the project folder. This is sufficient for known customer use cases and the effect maker.

*Update issue: *Since the uri for a specifics does not change, QML does cache the specifics. This means they are not updated if the source file changed.

The specifics for the effect maker regularly change. The workaround is to call the specifics
<TypeName>SpecificsDynamic.qml in this case and forward the source as a template to the front-end.

We can look for another workaround for this, but because of backwards compatibility we have to support SpecificsDynamic.

This means there can be a Pane, a Specifics or a SpecificsDynamic QML file for each component. Those are mutual exclusive. There is only one file per component.

Pane has precedence over SpecificsDynamic which has precedence over Specifics.

No custom template for types that have sheets
If there is a sheet we do not want to generate any custom template and the section should be empty.