Unimenu

NEW FEATURES
- SUPPORTS NOW ANY QT APP BY DEFAULT, no more need for making new modules in unimenu. 🚀
- print errors when command from unimenu fails, now runs commands in try except
- added unimenu.load_all_configs() which discovers all configs from the UNIMENU_CONFIG_PATH env var
- add custom data support to the config
- add unique id to menu nodes. not garantueed to be unique yet. example name PARENT1_PARENT2_LABEL
- add support for teardown for qt nodes. enabling you to remove the menu e.g. on plugin unload.
- added support for PySide6, to support modern apps such as CryEngine.
- swapped Autodesk Max & Maya to use Qt instead of their native menubuilders. much cleaner for Max, menus now don't persist across sessions.

POSSIBLE BREAKING BACKWARDS COMPATIBLE
renamed dcc to app in code.
if you e.g. use unimenu.dccs.qt, you now need to swap to unimenu.apps.qt
note that this doesn't affect top level methods. so you likely are good.

OTHER
- update [README](https://github.com/hannesdelbeke/unimenu/blob/main/README.md) & [wiki](https://github.com/hannesdelbeke/unimenu/wiki)
- update python version for pypi
- updated sample code any_dcc_test.py to include more features

correct versioning in package build
for release to pypi

the new unimenu now lets you create & modify menus with node trees, and when finalised, set them up in the app.

the new node based structure is much more flexible, and replaces the menubuilder approach from the first version.

unimenu also became more stable and consistent across several dcc's
with the upgrade, some apps haven't yet been tested due to my demo having run out. e.g. substance painter, marmoset, ...
as soon as i get my hands on them i'll test again