Allow user to override insecure setup codes and pair with homekit_controller

[bdraco]

Proposed change

Allow user to override insecure setup codes and pair with homekit_controller

User enters insecure setup code

User must re-enter insecure setup code and check the box before they can continue

Note that I tested this using two different instances thus the light and dark mode

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

Additional information

• This PR fixes or closes issue: fixes The default device homekit 123-45-678 setting code cannot be added #49154
• This PR is related to issue:
• Link to documentation pull request: Add Pairing with an insecure setup code section home-assistant.io#17937

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

To help with the load of incoming pull requests:

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

[Jc2k]

LGTM. Should we flesh out why we are doing this in the docs? Users might wonder why their device is insecure and if there is anything they can do. We can provide a bit of context about the error, maybe as an FAQ?

[bdraco]

LGTM. Should we flesh out why we are doing this in the docs? Users might wonder why their device is insecure and if there is anything they can do. We can provide a bit of context about the error, maybe as an FAQ?

Done here home-assistant/home-assistant.io#17937

[bdraco]

Retested. All looks good 👍

[bdraco]

Updated the screenshots as well