Automate building wheels for common build dependencies

[cdce8p]

Proposed change

Followup to

• Build wheels for build dependencies [ci] #126987
• Build common wheels wheels#807

By building wheels for common build dependencies, we can speed up the normal wheel build significantly. Without it, pip would create those wheel when installing the isolated build environments for dependencies, however those aren't cached / uploaded to wheels.home-assistant.io. Thus the wheel build would be run for each new dependency.

For full details, see description on home-assistant/wheels#807.

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[Thomas55555]

Suggested change

	# Only add build system requirements here or or dependencies
	# Only add build system requirements here or dependencies

[frenck]

This means we start building wheels for packages we do not use?!?

That makes no sense to me. We will end up wasting more time as we skip releases, besides, we will put up wheels we do not use...

../Frenck

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[cdce8p]

This means we start building wheels for packages we do not use?!?

They are used:

• When building wheels and any one of them is a requirement (or part of the build system)
• For any PR on the wheel builder repo
• When building new docker images

We will end up wasting more time as we skip releases

The workflow itself takes roughly ~10min (for all jobs) when no new wheels need to be build. It's run once per day to account for PRs to the requirements file (i.e. if new once are added there). This can be remove though if we trigger a workflow_dispatch event afterwards.
Aside from that, it's explicitly only run on dependabot PRs when a new version is released. Thus we don't waste resources there.