Centralize knx config and update xknx to 0.12.0

[marvin-w]

Breaking change

This change incorporates the following pull requests that have been merged to an intermediary branch in order to be able to merge them together to dev once done.

• Refactoring of configuration: Refactor KNX integration to centralize configuration yaml #39189
• Dependency Upgrade: Updates for xknx 0.12.0 #38880

Proposed change

• Refactor the xknx integration in order to comply with new configuration schema (ADR007).
• Update xknx to 0.12.0.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

knx:
  tunneling: 
    host: '192.168.0.1'
  cover: !include knx_cover.yaml
  climate: !include knx_climate.yaml
  light: !include knx_light.yaml
  binary_sensor: !include knx_binary_sensor.yaml
  switch: !include switch.yaml
  sensor: !include sensor.yaml
  notify: !include notify.yaml

Additional information

• This PR fixes or closes issue: fixes KNX Climate does not properly read status of KNX controlled A/C unit and some controls don't work neither #37137, fixes knx cannot map hvac target mode when set via homekit #36342, fixes KNX Climate: Target temp step size defaults to 0.1 degrees w/o setpoint_shift #32180, fixes XKNX Climate component still have little bugs #30419, fixes HASS.IO v0.97.1 Lovelace Card not displaying correct KNX Operation Modes #26624
• This PR is related to issue:
• Link to documentation pull request: Update documentation of KNX integration home-assistant.io#14299

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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @Julius2342, mind taking a look at this pull request as its been labeled with an integration (knx) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[marvin-w]

Can you please restart the CI pipeline? The error was unrelated to that change (and green in the original PR (#38880))

[marvin-w]

Thank you @frenck! There still appears to be an error with the cached virtual environments:

Cache not found for input keys: Linux-venv-3.7-1715f2d5fa43055d4c9f601445d0c767ac64822d152e8c870b198f0bb63980f4-5c90b0c1eb0904cdcc41364933d33f3a76986c9ebb6b665cbbd4a8efc97382f7-e9a553241391d0a2a8ad4725137d163e1e9a5664b55a5a27760765c447290717

[frenck]

I have no clue 🤷 Could you rebase your PR onto the latest dev branch please?

[marvin-w]

@frenck This PR is just a wrapper for two other PRs that have already been reviewed ( #39189 & #38880) and merged into an intermediary branch within HA. If I rebase onto the latest dev I'm effectively rewriting the history (and thus a force push is needed - for which I do not have sufficient permission).

@MartinHjelmare created the branch within HA yesterday. I could merge fast forward but since you specifically asked for a rebase I wanted to clarify first.

[frenck]

Rebased it.

[MartinHjelmare]

Great!

[SquaredCircleHunter]

It would be a nice addition to also allowing labels for knx includes

Analogous example to the one here:

knx:
  tunneling: 
    host: '192.168.0.1'
  light groups: !include knx-light-groups.yaml
  light switches: !include knx-light-switches.yaml

[MartinHjelmare]

If you want to suggest an enhancement please open a feature request in the Feature Requests section of our community forum.

Merged PRs should not be used for enhancement discussion or bug reports.

Thanks!