Modelbaker

- Fix issue with dialog/panel height calculation

- Fix basket selection widget on GeoPackage layers

- Info that on basket creation UUIDs are used as ids in the Dataset Manager and the note that the user might need to change them (see 599)
- Hide "Create Import Tid" in the GUI when it has no effects (in schema import dialog and the wizard) and only preserve it in the import data dialog.
- `--importBid` should be set on any update command. Since otherwise an update of a data from a model without stable BASKET IDs corrupts the previously imported data.
- `utils.gui_utils` (and merge ui.py into it) as a moduls to keep all the extended widgets, views and models that can be used by multiple gui components of the plugin and `utils.globals` to keep variables that are used by multiple parts of the plugin (not only gui) like CATALOGUESET

With the release 7.0. Model Baker introduces it's data validator as a new feature, but sets also a milestone after all those integrations in the last year like the UsabILIty Hub (6.5), the Wizard (6.6) and the proper handling of Baskets and Datasets (6.7).

Data Validator
Easy validation of the physical data against the ILI model. The data can be filtered by model, dataset or baskets.


The database connection parameter are emitted from the currently selected layer. Mostly this is representative for the whole project, since mostly a project bases on one single DB schema. In case of multiple used DB Schemas, it's possible to "switch" between the validation results when switching the layers.

`ili2db` is used with the parameter `--validate`, so no export of the data is needed. The output is parsed by Model Baker and provided in an interactive list.
Entries of the type `Error` and `Warning` are listed.

With right click on the error there is opening a menu with:
- Zoom to coordinates (if coordinates are provided)
- Open form (if a stable t_ili_tid is available)
- Set to fixed (marking the entry mark green to have organize the fixing process)

Use List Widget for ARRAY mapping
If the metaattribute `!!ili2db.mapping=ARRAY` is defined in the ILI model configure the corresponding widget in QGIS as "List".

- Fix the importTid/exportTid handling in the wizard: Get the `TidHandling` from settings table to decide if `--importTid` / `--exportTid` needs to be passed on data import/export. `TidHandling` is in the `t_ili2db_settings` table when `--createTidCol` is passed on schema import.
- Set t_ili2db_basket table to writable: Since Model Baker does not create always the BIDs correctly.
- Use fetch and increment of T_Id in geopackage: Considering the `T_KEY_OBJECT` table simulating a global sequence number. This is used because we edit the dataset and basket table.

Catalogue dataset handling in wizard
On importing data you can mark a file as catalogue. If so, then there is no dataset selectable.
The data is imported to a dataset called `Catalogueset`. It stays technical and it's hidden for the user (It's not listed in the Dataset Manager, it's not listed in the Dataset Selector and it's not listed as option in the Relation Reference of the basket ids. On export it's not listed as dataset).

Export of baskets / models / datasets in wizard
On the data export page of the wizard you can filter for model(s) but also dataset(s) and basket(s).
In the ili2db doc they say you can use models or alternatively datasets or baskets (so this implies that you only use usually one of them). And it makes no conjunction (AND) but a disjunction (OR) if multiple parameters are given. A conjunction can still be done by selecting the smallest instance (baskets).

Getting catalogues from the UsabILIty Hub
On entering the _Import Schema Configuration Page_ the ilidata.xml on the UsabILIty Hub repositories are parsed for the modelnames (from the listed models) and the type `referenceData` in the `categories`. There the `modelLink` properties are read and the models are loaded into the list of models to import automatically.

On the _Import Data Configuration Page_ we have an autocomplete drop down containing the `referenceData` items (transfer files) found according all the models in the current database schema (not only the previously imported ones). You can add and remove them by +/-. `xml` files receive the default property that they are catalogues (considering the datasets).