Rename zeroconf service info

[epenet]

Proposed change

Rename HaServiceInfo to ZeroconfServiceInfo.
As discussed in #58958 (comment)
cc @frenck @bdraco @KapJI

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.

[epenet]

Or maybe we could use ZeroconfDiscoveryInfo to match the generic DiscoveryInfoType?

Suggested change

	class ZeroconfServiceInfo(TypedDict):
	class ZeroconfDiscoveryInfo(TypedDict):

[frenck]

I think the current suggestion (ZeroconfServiceInfo) is fine. It matches what is represented in Zeroconfig itself.

If anything, I would maybe even call it just "ServiceInfo", as it is already in the Zeroconf package namespace.

[epenet]

Should I wait for @bdraco to confirm that he too prefers just ServiceInfo?
I've marked the other PRs as draft until this one gets merged.

[bdraco]

I like the ZeroconfServiceInfo name because there are some integrations that have multiple discovery sources and it will easier to differentiate with something like SSDPServiceInfo, DHCPserviceInfo.

[frenck]

I'm ok with that :)
Do you approve otherwise @bdraco ?

[bdraco]

LGTM