Remove ability to ignore coverage violations

[epenet]

Proposed change

Remove ability to ignore coverage violations

Loosely based on #86534, this ensure that platforms we defined as "needs coverage" cannot be ignored.

Note: this will likely result in a slight drop of overall coverage.

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

[emontnemery]

Do we need to adjust the coverage target for codecov/project/required?

[epenet]

Do we need to adjust the coverage target for codecov/project/required?

I used the same settings as config-flow.
Isn't the objective 100% ?

[epenet]

Note: codecov/project/required is set to auto, and it's the first time it's being implemented so the failure is expected.
From now on, we would expect coverage to only go up for required...

[epenet]

cc @frenck / @MartinHjelmare / @thecode based on discussion on Discord.

[frenck]

LGTM! 👍

@MartinHjelmare ?

[MartinHjelmare]

Looks good!