Latest `pyside6` (6.7.0) breaks `traitsui`

Hi,
our CI picked up a problem when using latest `traitsui` version on Windows using python `3.11`. One of it's (optional) dependencies `pyside6` released breaking changes on the 9th of April with [version 6.7.0](https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.7.0).

````python
tests\unit\test_alias_manager.py:46: in test_gui
with tester.create_ui(alias, {"view": alias_edit_view()}):
C:\Python311\Lib\contextlib.py:137: in __enter__
return next(self.gen)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\testing\tester\ui_tester.py:105: in create_ui
ui = object.edit_traits(**ui_kwargs)
.hatch\all.py3.11-pyside6\Lib\site-packages\traits\has_traits.py:1811: in edit_traits
return view.ui(
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\view.py:457: in ui
ui.ui(parent, kind)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\ui.py:234: in ui
self.rebuild(self, parent)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\toolkit.py:168: in ui_live
ui_live.ui_live(ui, parent)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_live.py:52: in ui_live
_ui_dialog(ui, parent, BaseDialog.NONMODAL)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_live.py:72: in _ui_dialog
BaseDialog.display_ui(ui, parent, style)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_base.py:294: in display_ui
ui.owner.init(ui, parent, style)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_live.py:103: in init
self.create_dialog(parent, style)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_base.py:252: in create_dialog
self.control = control = _StickyDialog(self.ui, parent)
.hatch\all.py3.11-pyside6\Lib\site-packages\traitsui\qt\ui_base.py:135: in __init__
self.setLayout(layout)
E TypeError: 'PySide6.QtWidgets.QWidget.setLayout' called with wrong argument types:
E PySide6.QtWidgets.QWidget.setLayout(QVBoxLayout)
E Supported signatures:
E PySide6.QtWidgets.QWidget.setLayout(PySide6.QtWidgets.QLayout)
````

PS: I know this is technically a duplicate of #2044 but the problem is more generic and I thought this issues title is more to the point.