Support songpal wireless-only soundbar identifiers

[Flameeyes]

Proposed change

As shown in #64868, a number of newer models don't come wiht a macAddr
attributes, so for those fall back to the wireless address.

This could be hidden by the python-songpal library but for now this will
make it possible to have multiple modern songpal devices on the same
network.

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 Songpal not generating unique ID #64868
• 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 @rytilahti, @shenxn, mind taking a look at this pull request as it has been labeled with an integration (songpal) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Looks good!

[MartinHjelmare]

Should we tag it for a patch release?

[Flameeyes]

I think it would be fine to be in a patch release. But I'm not entirely sure whether the fact that entities might go from "no unique id" to "have unique id" would complicate things.

(The unique ID is only changed for entities that currently wouldn't have one, because they don't have a wired address — that's why it prefers the wired mac as unique identifier.)

[MartinHjelmare]

A possible complication would be if the user would roll back the update, the entity registry would still have the entry with the unique_id and not allow the entity without the unique_id to get its old entity_id but generate a new entity_id with a suffix.

[rytilahti]

Is non-backwards compatibility a blocker here, and if yes, what is be the proper way to solve this? My personal opinion is that this is ready to go as the pros clearly outweigh the cons. Also, I don't think most of the other integrations do offer a working downgrade path either..

[MartinHjelmare]

We should definitely merge this. It's just a question of do we include it in a patch release?

[rytilahti]

Ah, sorry for being unclear. My previous comment was for getting this into the next patch release, but I'll ping on discord to get another opinion on that.