Abort Shelly setup if MAC address mismatch

[thecode]

Proposed change

Recently bumped aioshelly to version 6.0.0 now reports if the supplied MAC address doesn't match the one read from the device under /shelly endpoint. This may happen due to DHCP address change while Home Assistant is offline, full details in home-assistant-libs/aioshelly#415

With this change we abort setup and when new IP address is updated (either by DHCP or mDNS) the device is init with the new IP.

Tested on Shelly 2.5 & Shelly Pro 2PM

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 Device Connection error, seems to mix IP addresses #97519
• 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]

Hey there @balloob, @bieniu, @chemelli74, @bdraco, mind taking a look at this pull request as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign shelly Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

Also this problem affects nearly every integration where there are multiple devices of the same type

Some recent text from the esphome pr I just opened:

This is a more general problem as #97457 (tplink) and #92955 (lifx) also have the same problem. This solution is similar to the used in flux_led

core/homeassistant/components/flux_led/__init__.py

Line 196 in 3e7ec88

# The device is offline and another flux_led device is now using the ip address

except for ESPHome we allow the name or the mac to change (for device replacement), but not both at the same time.

[bdraco]

Tested on a us plug

[thecode]

Thanks!