Update to pyunifi 2.12

[finish06]

Description:

Attempted to add improved exception handling within pyunifi. The pyunifi package will now attempt to log in if an access error is encountered. Additionally, the package will try 5 times for the unifi server to be brought back up in 1 minute intervals prior to giving up.

If the end user decides to not use a verified ssl certificate, the pyunifi package will now spit out warnings every time it sends a request as was requested by @balloob.

Related issue (if applicable): fixes #

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

Example entry for configuration.yaml (if applicable):

No changes

Checklist:

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

• Documentation added/updated in home-assistant.github.io

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

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
• New dependencies are only imported inside functions that use them ([example][ex-import]).
• New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Local tests with tox run successfully. Your PR cannot be merged unless tests pass
• Tests have been added to verify that the new code works.

[mention-bot]

@finish06, thanks for your PR! By analyzing the history of the files in this pull request, we identified @kk7ds, @fabaff and @kellerza to be potential reviewers.

[balloob]

If the end user decides to not use a verified ssl certificate, the pyunifi package will now spit out warnings every time it sends a request

Isn't this avoidable by setting verify=False when making a request ?

[balloob]

Cherry-picked for 0.44.1