Add regex matching to zeroconf service names

[jcalbert]

Home Assistant release with the issue: 0.101.0.dev0

Last working Home Assistant release (if known): N/A

Operating environment (Hass.io/Docker/Windows/etc.): N/A

Description of problem:
Per home-assistant/core#27371 (comment), home-assistant/core#27371 (comment), home-assistant/core#27371 (comment)
Add regex matching for devices with specimen-unique zeroconf service names.

example:
Rainforest Automation's device's zeroconf have the form
eagle-012abc._http._tcp
so the associated zerconf entry in manifest.json would be
"zeroconf": ["eagle-[0-9a-f]{6}._http._tcp.local."],

Additional information:

[balloob]

I agree that we should do this.

I don't like overloading the type with a name regex. I think that we should go for something like this:

"zeroconf": [
  { "type": "_http._tcp", "name": "eagle-[0-9a-f]{6}._http._tcp.local."}
]

This can be made backwards compatible by assuming string values are just types. Name is optional.

[frenck]

This has been implemented, not with regular expression, but we have wildcard support (*), which has been proven sufficient for our use case.