Remove repair issue for MQTT discovered items

[frenck]

Proposed change

This PR reverts/removes the creation of repairs issues for the MQTT integration, on entities that are created by MQTT discovery, as introduced in Home Assistant 2023.8.

• These repair issues seem to cause/trigger quite a lot of fuzz that should not be needed; there are quite a lot of topics across different socials on this.

• This repair issue is mostly misunderstood as a breaking change, while it is not breaking at all. The original intent was to inform and to get people to report issues upstream to third-party software that integrate with Home Assistant over MQTT. It is currently handled gracefully and in a backward-compatible manner for the end-user.

• Repair issues must be fixable by the user; however, in this case, it currently isn't actionable by most users as most discovery payloads aren't created by users but by the third-party software.

• One of the bigger pieces of software triggering this issue, is Zigbee2MQTT. An adjustment for this missed their release cut, meaning these users get these repairs too (which is a big part of our community).

• The goal of getting MQTT naming up to par with the rest of the Home Assistant integrations remains; This in order to support a better and more standardized naming of entities and devices across Home Assistant (so we can provide better naming depending on the user context in the future).

ℹ️ Marking this PR for the 2023.8.4 patch release that is planned for the 24th of August.

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 #
• 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 @emontnemery, @jbouwh, mind taking a look at this pull request as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt 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 mqtt Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[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.

[jbouwh]

I see you corrected things

[jbouwh]

LGTM,
Thnx @frenck 👍