more precise, the problem here is the following:
Creating a UnoControlTabPageModel at the global service factory gives you a component which supports what is requested in the service description, plus everything which normally is only available in control models which are embedded into a dialog.

For instance, an css.awt.UnoControlEditModel, created at the global service factory, has no properties PositionX, PositionY, Width, Height, and some more. However, if you use the XMultiServiceFactory interface of a UnoControlDialogModel, and create an css.awt.UnoControlEditModel there, then the resulting component will have those properties, so it can be used as child of the dialog model.

For a tab page model, already the instance created at the global service factory supports those properties, which is a) inconsistent and b) likely to lead to problems when the model is to be used in a context other than a dialog (for instance, within documents, as form control).

Fixing this means that the tab page model created at the global service factory needs to not support those dialog-related properties, and the dialog itself must be able to create such an "extended" version of the tab page model, as it already does with all other model types.

However, since a tab page model is create with arguments (in opposite to all other so-far existing control models), the XMultiServiceFactory::createInstanceWithArguments implementation of the dialog model must be modified to *not* ignore its arguments - currently, it is completely agnostic of them.

done in CWS gridfixes

fs->tkr: please verify in CWS gridfixes

Looks good -> verified.

getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.