Fix the issues found in the review of 1.0.2

[DAB-LABS]

I had 1.0.2 reviewed the same way as the last two. Nothing in how the library talks to devices changed, and the review confirmed that again.

It did find an issue when a device's session key expires and the device has since been locked in the app, the library tried to log in again, failed, and raised the login failure instead of the error the device gave the original request. The original library never tried to log in again, so a program written against it, including Home Assistant, handles the first error and may have never seen the second. That is fixed, along with some smaller items.

Tested on Python 3.13 and 3.14, 261 tests, plus a live run against an RM4 Pro.

Coding assistant's notes on this change:

When re-authentication after an expired-key answer fails, the request's own reply is now returned, so the caller sees the same AuthorizationError or ConnectionClosedError the original library raised. The failure is logged at debug level. The README now states this contract and its worst case: one call can wait out up to three timeouts (the request, the authentication, and the repeat).

Also in this change: the authentication generation is read under the request lock, so a request queued behind auth() cannot skip a re-authentication it needs; aclose() racing an endpoint that is still opening no longer leaks the new socket; a new capture window re-checks for a rival claimant after giving the finalizer its turn; CapturedSignal.pulses and ParsedPacket.pulses are tuples, so the frozen dataclasses are hashable; check_error unpacks the error code as little-endian explicitly; the locks are created in init; send_packet accepts bytearray; setup() goes through a public send_setup_packet() helper; the CLI closes its device; and the README adds the A2 and the Hysen HY02/HY03 to the device list. A typing pass (py.typed, mypy in CI) is left for 1.1.