Streamline setup of deCONZ button platform

[Kane610]

Breaking change

Proposed change

Utilise the improvements from refactoring pydeconz to stream line platform setup.

• Streamline setup of deCONZ alarm control panel platform #70589
• Streamline setup of deCONZ button platform #70593

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

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.

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.

[bdraco]

If there will ever be a lot of scenes at startup....you could make async_add_scene a wrapper around new async_add_scenes and accept multiple so you only call async_add_entities once with all the entities

[Kane610]

Is it that big of a deal for upstart? I'm not questioning your reasoning but Id really like to understand what you're suggesting

[bdraco]

Every time you call async_add_entities its going to call https://github.com/home-assistant/core/blob/dev/homeassistant/helpers/entity_platform.py#L326 which creates a task in the event loop.

If you had 100s of scenes (hopefully someone doesn't actually have that many), this can start to add up quickly

[Kane610]

I can't say for other users. But I could definitely see myself using maybe 4 scenes per group that are relevant to control over various times of the day. So maybe at least 40 scenes would be expected.

[Kane610]

Thanks! I will consider this going forward