ZHA bump 2026-10-29 #3

## Proposed change

This bumps ZHA to [2.4.2](https://github.com/zigpy/zha/releases/tag/2.4.2), a small bugfix release. zha-quirks stays at 2.4.0.

- ZHA [2.4.2](https://github.com/zigpy/zha/releases/tag/2.4.2) (from 2.4.1), full diff: https://github.com/zigpy/zha/compare/2.4.1...2.4.2

These dependency upgrades come with it, as they are pinned by ZHA:

- `zigpy-deconz` [1.1.1](https://github.com/zigpy/zigpy-deconz/releases/tag/1.1.1) (from 1.1.0), full diff: https://github.com/zigpy/zigpy-deconz/compare/1.1.0...1.1.1

`zigpy`, `bellows`, `zigpy-znp`, `zigpy-xbee`, `zigpy-zigate` and `zigpy-ziggurat` are unchanged.

### Changes in these releases

Relevant changes in these releases for HA Core:
- **ZHA starts again on ConBee II / RaspBee II** (zigpy-deconz): zigpy 2.4 registers a Green Power endpoint next to the existing two, but this firmware only has two endpoint slots, so startup failed with `No available endpoint slots exist` (home-assistant/core#189366)
- Requests sent after the radio disconnected now fail cleanly instead of logging an `AttributeError` traceback (zigpy-deconz)

Note about other ZHA changes (irrelevant for HA Core): new device diagnostics in ZHA's test database, and its tests now run against zha-quirks 2.4.0.

### Changes in the ZHA integration for this:
- None needed: the pin bump and regenerated requirements only

## Type of change

- [x] 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: 
- Link to contributors documentation pull request: 
- Link to frontend pull request: 

## Checklist

- [ ] I understand the code I am submitting and can explain how it works.
- [ ] The code change is tested and works locally.
- [x] 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][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
- [ ] Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]

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

- [x] The [manifest file][manifest-docs] has all fields filled out correctly.  
      Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.  
      Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

- [ ] I have reviewed two other [open pull requests][prs] in this repository.

[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure

[dev-checklist]: https://contributors.home-assistant.io/core/development/checklist/
[manifest-docs]: https://contributors.home-assistant.io/core/integrations/manifest/
[quality-scale]: https://contributors.home-assistant.io/core/quality-scale/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://contributors.home-assistant.io/start/pull-requests/#before-you-open-it