Improve discovering upnp/igd device by always using the SSDP-discovery for the Unique Device Name

[StevenLooman]

Proposed change

Instead of using/storing the UDN from the device description, store the UDN from the SSDP discovery. The latter is used to find the device when initializing the component. Normally, the UDN should be the same in both the SSDP communication and the device description, but alas, broken UPnP implementations exist.

This should fix #110216, and hopefully not break any existing installations. If any new issues arise after this change, the plan is to revert this change.

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 Upnp - Device not discovered #110216
• 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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[StevenLooman]

If possible, please don't add this to 2024.2.4, but rather add this to the 2024.3.0 beta. A bit of more testing cannot hurt.

[Kane610]

If youre insecure about the end result of this change maybe not put it in milestone 2024.3.1?

[StevenLooman]

I feel confident enough to include it now.

At the time when I created this PR there was no 2024.3.b0 milestone, only one for 2024.2.

[MartinHjelmare]

Please limit docstring lines to 72 characters per line, in accordance with PEP8.

The first line is a header and should be a single sentence. After that an optional body can follow separated from the header by a blank line.