Check if requirements are installed in the executor

[bdraco]

Proposed change

May help with #71575

pkg_util.is_installed does I/O, it should run in the executor

This got rid of many more asyncio warnings when a component was discovered or startup was happening on a slow disk

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 #
• 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.

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.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[bdraco]

Still need to get back to this

[bdraco]

Too many irons in the fire this month

[bdraco]

Retest looks good. Less I/O starvation at startup. This won't address the CPU being bound on the GIL issues at startup, but making all that better is slow grinding incremental process. We will never be able to fix the problem where we have to load python files from disk in the event loop though as there are so many packages that make assumptions that they are loaded in the thread the event loop is running. We could make that better with a limit to how many we load at the same time but the tradeoff is slower startup