Add setup type hints [g]

[epenet]

Proposed change

As follow-up to #63098, add more setup type hints.

These components needed a few tweaks to pass mypy.

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.

[probot-home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (group) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-home-assistant]

Hey there @mletenay, @starkillerOG, mind taking a look at this pull request as it has been labeled with an integration (goodwe) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[frenck]

Was just thinking, this makes it Any, which is suboptimal as well.

This works better:

Suggested change

	component = hass.data[DOMAIN]
	component: EntityComponent = hass.data[DOMAIN]

It does reveal new issues though.

[epenet]

Three options:

1. take it out of [g] and treat it separately
2. keep is as Any and consider a follow-up PR
3. continue fixing here

I'm inclined to do option 1

[frenck]

🤷 depends on the changeset.

I'm fine with 1 or 3, 2 is a bit tricky actually as everything seems fine but isn't.

[epenet]

I have reverted the changes to group.
It looks like it will need quite a bit of work to get working.

[epenet]

(and as a bonus it should make CI run partial instead of full)

[frenck]

It does :)
Pretty darn happy with that CI stuff nowadays 👯