Refactor pihole integration

[johnluetke]

Breaking Change:

This change requires existing configurations for the pi_hole integration to be moved from sensor platform key to a pi_hole top level key.

• monitored_conditions is removed
• pi_hole configuration block defines host, port, location and ssl options

configuration.yaml before this change:

sensor:
  - platform: pi_hole
    host: pi.hole
    monitored_conditions:
      - ads_blocked_today
      - ads_percentage_today
      - dns_queries_today
      - domains_being_blocked
      - queries_cached
      - queries_forwarded
      - unique_clients
      - unique_domains

configuration.yaml after this change:

pi_hole:
  host: pi.hole

Description:

Refactors the pi_hole component from a single sensor to an integration with a sensor platform. This allows services, switches, and possibly other entities to be added to the integration in a future pull request.

Pull request with documentation for home-assistant.io: home-assistant/home-assistant.io#10097

Example entry for configuration.yaml (if applicable):

pi_hole:
  host: pi.hole

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[probot-home-assistant]

Hey there @fabaff, mind taking a look at this pull request as its been labeled with a integration (pi_hole) you are listed as a codeowner for? Thanks!

[johnluetke]

Notes for reviewer: This change lays the groundwork for future functionality i intend to add to the integration shortly after approval. This change itself introduces no new functionality to the integration.

[pvizeli]

You can use discovery to setup sensor from component without need a config for this

[johnluetke]

Quick update: I'm still working on working out the tests portion of this change. My day job has been demanding this past week

[johnluetke]

@fabaff @balloob @MartinHjelmare @pvizeli I believe I have addressed all the concerns raised

[johnluetke]

@MartinHjelmare Requested changes have been made and are ready for re-review

[MartinHjelmare]

Looks good!

[MartinHjelmare]

Can be merged when build passes.

[MartinHjelmare]

Please update the config example and breaking change paragraph in the PR description. Please describe briefly what changed and what the user needs to do to cope with the breaking change.

[MartinHjelmare]

We don't require a sensor platform config after this PR. We set up the sensor platform via discovery from the pi_hole component module. I've updated the breaking change paragraph and config examples.