UniFi integration move to push messaging

[Kane610]

Proposed change

This PR moves UniFi integration from polling data during normal operations to use web socket signalling. This hopefully solves the issue where the integration seem to happen in a never ending loop requesting more data from UniFi leading to HASS being unusable.

• Fix signalling of new clients/devices
• Fix reconnection logic
• Fix tests

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

Additional information

• This PR fixes or closes issue: fixes HA Stops Responding (Unifi Integration Related) #30168

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[MartinHjelmare]

Nice!

[Kane610]

@MartinHjelmare additional thoughts here?

[MartinHjelmare]

Looks good!