Add check for integration config schema to hassfest

[emontnemery]

Proposed change

Add check for integration config schema to hassfest

Background:

Integrations which can be setup via YAML but don't support any configuration parameters commonly don't declare any CONFIG_SCHEMA. This means useless configurations such as this won't be warned against:

api:
   blah # Not supported by the `api` integration

Also, there is no warning if integrations which can not be setup via YAML are referenced in the configuration.
There are two cases, integrations which define an async_setup or setup but can't be setup via YAML and integrations which don't declare async_setup or setup.

Suggestion:

• Enforce that integrations with async_setup or setup has either of CONFIG_SCHEMA, PLATFORM_SCHEMA, PLATFORM_SCHEMA_BASE or a config platform
  • Implemented in this PR
  • Existing integrations which fail the new check should either declare an empty schema if setup via yaml is possible (for example api), or a schema which logs a warning / repair saying yaml configuration is not supported (for example discord)
    Updating integrations will be handled in separate PRs
• For integrations which do not have async_setup or setup but are referenced in the config we log a warning / repair
  • Detect attempt to setup config entry integration via YAML #93589

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.