Aioharmony

- Fixed:
- "module asyncio has no attribute coroutine" exception in call_raw_callback function on Python 3.11
- Changed:
- Bumped minimum required Python version to 3.9

Fixed: Fixed exception in Python 3.10 by removing loop parameter (swolix)

Changed: Get remote_id from Hub without creating websocket connection

- Fixed: Registered handlers would not be unregistered after a timeout when sending commands to HUB.
- Updated slixmpp from >= 1.5.2 to >= 1.7.0
- Updated aiohttp from >= 3.4 to 3.7.3

- Fixed: When using XMPP protocol the switching of an activity was not always discovered.
- Fixed: Call to stop handlers will now be called when timeout occurs on disconnect
- Changed: ClientCallbackType is now in aioharmony.const instead of aioharmony.harmonyclient.
- Changed: default log level for aioharmony main is now ERROR
- New: callback option new_activity_starting to allow a callback when a new activity is being started (new_activity is called when switching activity is completed)
- New: 3 new HANDLER types have been added:
- HANDLER_START_ACTIVITY_NOTIFY_STARTED: activity is being started
- HANDLER_STOP_ACTIVITY_NOTIFY_STARTED: power off is started
- HANDLER_START_ACTIVITY_NOTIRY_INPROGRESS: activity switch is in progress
- New: Protocol to use can be specified (WEBSOCKETS or XMPP) to force specific protocol to be used. If not provided XMPP will be used unless not available then WEBSOCKETS will be used.
- New: protocol used to connect can now be retrieved. It will return WEBSOCKETS when connected over web sockets or XMPP.
- New: One can now supply multiple IP addresses for Harmony HUBs when using aioharmony main.
- New: option activity_monitor for aioharmony main to allow just monitoring of activity changes
- New: option logmodules for aioharmony main to specify the modules to put logging information for

Fix for sending command to device when using XMPP protocol