Modify TelegramQueue.Callback filter from HA service

[farmio]

Description

• knx_event: renamed fire_event_filter to event_filter and deprecated fire_event config option. A callback is now always registered for HA to be able to modify its group_addresses filter from a service.
• added knx.event_register service allowing to add and remove group addresses to trigger knx_event without having to change configuration.
• TelegramQueue.Callback: add group_addresses attribute to store a list of GroupAddress triggering the callback (additionally to address_filters).

So now the yaml configured filters live in Callback.address_filters and the group_addresses added by knx.event_register live in Callback.group_addresses.

With this it is possible to build automations using knx_event on the fly without changing or even reloading configuration.
So an HA automation could listen to automation_reloaded

automation:
  trigger:
    platform: event
    event_type: automation_reloaded
  action:
    service: knx.event_register
    data:
      address: "1/2/3"

to setup a group address listener for itself and later on use the registered knx_event. I think this could come in handy with blueprints.

This fits nicely to #497

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• The documentation has been adjusted accordingly
• The changes generate no new warnings
• Tests have been added that prove the fix is effective or that the feature works
• The changes are documented in the changelog
• The Homeassistant plugin has been adjusted in case of new config options

[coveralls]

Coverage increased (+0.005%) to 94.877% when pulling 7ee9768 on farmio:dynamic_knx_event into 4379417 on XKNX:master.

[farmio]

🤔 It strikes me that it is not possible to use multiple trigger-action blocks in one automation. Who knew?
Well, maybe this will get changed in the future, I think the service can be useful nevertheless - even if only for testing purposes.

OK so now I think this is totally possible using choose in the action: block and trigger.platform or trigger.event in its condition. 🚀

[farmio]

This is kind of hacky 😬
I guess if Callback is instantiated with no filters (not even empty Lists) its not meant to be changed.
I'm open for suggestions 😉