Detect Early Access versions of UniFi Protect and Warn User

[AngellusMortis]

Proposed change

Since UniFi Protect does not have an open API, an Early Access version of Protect can have a breaking change at any time causing the HA integration to break. The repair system can be used to have the user to acknowledge the risk of using EA versions.

Warning repair you get for running EA:

If you submit while still running EA, second warning:

If an error occurs during startup while running EA, the above Repair will be deleted and replaced with:

(note: Error: test is the str(Exception), I only had just did raise Exception("test") so that is why it is kind of bland.

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)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @briis, @bdraco, mind taking a look at this pull request as it has been labeled with an integration (unifiprotect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifiprotect can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign unifiprotect Removes the current integration label and assignees on the issue, add the integration domain after the command.

[bdraco]

I think we could raise a different repair issue if the setup fails on ea

bdraco@ddf0628

[bdraco]

I'm pretty comfortable with this now. I think its ready for tests

[bdraco]

Still fighting with the cloud key to get it updated to EA

[bdraco]

I've got the cloudkey factory reset now and running
UCK G2 Plus v3.0.12

I'm updating protect to 2.6.17 to test this

[bdraco]

Looks like its working as expected.

Going to restart now to make sure it doesn't come back

[bdraco]

Found an issue in testing but its not related to this change #82041

[bdraco]

Testing looks good 👍

[bdraco]

Thanks @AngellusMortis