Fix wirelesstag unique_id to use uuid instead of tag_id

[sergeymaysak]

Proposed change

This is fix for the issue 97736

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 Wirelesstags does not produce uinique IDs and uses wrong "Id" to produce them #97736
• 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 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[frenck]

@sergeymaysak There is no need to constantly merge dev into this PR (unless there is a conflict or a long time has passed). This is now effectively blocking merging and wasting unneeded CI resources. Let's do it a little less 😉

[sergeymaysak]

@sergeymaysak There is no need to constantly merge dev into this PR (unless there is a conflict or a long time has passed). This is now effectively blocking merging and wasting unneeded CI resources. Let's do it a little less 😉

Sure, no prob )

[edenhaus]

Thanks @sergeymaysak 👍

Comments addressed

[MartinHjelmare]

Please address the comment in a new PR. Thanks!