SSDP matching improvements

[scop]

Breaking Change:

ssdp in manifest.json has changed; it is now a list of dicts, and as we now match using the UPnP device description fields directly, device_type has to be renamed to deviceType. Not sure if custom integrations support this stuff in the first place, but if they do, they need to adjust accordingly. No included integrations use it at the moment, nor are they broken by this change.

Description:

Per discussion in #28214 (comment)

• support multiple match groups per domain
• require matches on all, not any item in a group
• support matching on all UPnP device description data

Matching on all UPnP device description data is consistent with providing all of it, ditto the ssdp data structure in manifest.json to the corresponding provided discovery_info, see #28197

Related issue (if applicable): #28214

Pull request with documentation for developer docs: home-assistant/developers.home-assistant#341

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[scop]

This has some issues still, will address, marking as WIP meanwhile.

[scop]

WIP lifted, hopefully got it right now.

[balloob]

🎉

[scop]

Thanks!