Add custom integration block list

[emontnemery]

Proposed change

Add custom integration block list

The block list is a dictionary where the key is the integration domain and the values have a reason why the integration is blocked, as well as the lowest version which is not blocked.

Background in #112464

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

[MartinHjelmare]

Just add a test.

[bdraco]

2024-03-06 00:49:59.608 WARNING (SyncWorker_15) [homeassistant.loader] We found a custom integration start_time which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-03-06 00:49:59.608 ERROR (SyncWorker_15) [homeassistant.loader] Version 1.1.6 of custom integration 'start_time' breaks Home Assistant and was blocked from loading, please create a bug report at https://github.com/AlexxIT/StartTime/issues

👍
Nice!

[cdce8p]

Should we provide a way to overwrite this? Especially if lowest_good_version is set to None this essentially means that users won't even be able to install a newer (fixed) version until our mapping has been updated and they update their Home Assistant version.

It might also make testing blocked integrations itself to provide a fix more difficult without it.

--
The safe alternative of course would be to specify the last know bad version with the drawback that even newer ones might be broken.

[emontnemery]

@cdce8p there are a thousand ways to overcome the block list, users can manually change the version in the manifest, rename the integration, make a custom integration which clears the block list etc. etc., I don't think we also need to provide some official way.

[cdce8p]

@cdce8p there are a thousand ways to overcome the block list, users can manually change the version in the manifest, rename the integration, make a custom integration which clears the block list etc. etc., I don't think we also need to provide some official way.

At least changing the version won't work if lowest_good_version is set to None but renaming is still an option.