Fix setup error for logbook

[springstan]

Breaking Change:

Description:

• caused by: Move imports to top for homekit #29560
• fixed by moving imports back into the setup function of the homekit integration

Related issue (if applicable): fixes #29845

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

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

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

• Documentation added/updated in home-assistant.io

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

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

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[springstan]

I do not know why the logbook fails to setup when the imports are at the top for the homekit integration.
It seems to be unrelated but somehow moving them back resolves the mentioned issue.
Any insight or investigation in this issue is appreciated :)

[balloob]

Logbook imports homekit constants. In Python, importing homeassistant.components.homekit.const means we'll import homeassistant.components.homekit, homeassistant.components etc because each part of the module path is either a file or a variable in that module.

[balloob]

We shouldn't revert it but instead add homekit to the after_dependencies of Logbook. I've added a PR #29491 for 104 that will make sure that those requirements are installed too.

It's annoying because really we should turn it around, have homekit register itself with logbook on how to render its events.

[springstan]

@balloob okay thanks for the clarification on this issue, will close it now.

[springstan]

It is probably the best to solve this error in one PR instead of splitting it into two and therefore I reopened this PR to solve this problem by adding homekit as a after dependency to logbook as suggested by @balloob.

[balloob]

I've opened #29913 to better explain the issue and list things to solve to get to a solution.

I will go ahead and approve this PR today because we can hot fix this to get 103 working.

[balloob]

I did add it to the milestone but really that can only work if we can also include #29491 , so tagged that one too.