QUOTA_EXCEEDED is not mapped to TooManyRequestsError, so rate limiting arrives untyped

从 response_handler.py 中的三个错误映射和 check_response 开始检查，尤其是第 60 行附近现有的 TooManyRequestsError 映射。复现 issue 中的 FakeResp 用例，然后验证 QUOTA_EXCEEDED 响应会引发 TooManyRequestsError，而不是通用的 OverkizError。实际的速率限制响应与预期的 back-off 路径保持一致的类型，即表示完成。

🐛 The problem

The Overkiz cloud reports its polling quota with errorCode: QUOTA_EXCEEDED, which matches none of the three error maps in response_handler.py, so it falls through to the generic raise at the end of check_response:

pyoverkiz.exceptions.OverkizError: {'errorCode': 'QUOTA_EXCEEDED', 'error': 'Too many requests, try again later'}

TooManyRequestsError is only reachable for a different errorCode (response_handler.py:60):

("AUTHENTICATION_ERROR", "Too many requests", TooManyRequestsError),

So the one exception type that means "you are being rate limited" is never raised for the server's actual rate-limit response.

🔁 Reproduction

import asyncio
from pyoverkiz.response_handler import check_response
from pyoverkiz.exceptions import OverkizError, TooManyRequestsError

class FakeResp:
    status = 403
    url = "https://example/events/x/fetch"
    async def json(self, content_type=None):
        return {"errorCode": "QUOTA_EXCEEDED",
                "error": "Too many requests, try again later"}

async def main():
    try:
        await check_response(FakeResp())
    except TooManyRequestsError:
        print("typed")
    except OverkizError as err:
        print("untyped:", err)

asyncio.run(main())   # -> untyped: {'errorCode': 'QUOTA_EXCEEDED', ...}

Why none of the maps catch it:

• _ERROR_CODE_MESSAGE_MAP (:47) — has no QUOTA_EXCEEDED entry
• _MESSAGE_FALLBACK_MAP (:104) — has "Too many executions" and "Too many attempts with an invalid token", but not "Too many requests"
• _ERROR_CODE_FALLBACK_MAP (:121) — only AUTHENTICATION_ERROR and RESOURCE_ACCESS_DENIED

📉 Why it matters

Callers cannot distinguish rate limiting from an unknown server error without string-matching the payload, so any back-off keyed on TooManyRequestsError silently never runs.

Measured on an Atlantic Cozytouch V2 hub (cloud API), eight commands issued in parallel to eight heaters, Home Assistant's overkiz integration:

Because the error arrives untyped:

• it surfaces as Unexpected error fetching device events data with a full traceback, rather than a handled rate-limit path
• the coordinator keeps polling at the interval that hit the limit instead of slowing down
• the failed update marks every entity unavailable, and Home Assistant then refuses the remaining service calls — Referenced entities ... are missing or not currently available — so three commands were silently dropped
• worst state-delivery lag in that run was 28.97 s

✅ Suggested fix

Either map the code directly in _ERROR_CODE_MESSAGE_MAP:

("QUOTA_EXCEEDED", None, TooManyRequestsError),

…or, more robustly, add the message to _MESSAGE_FALLBACK_MAP so it matches whatever errorCode carries it:

("Too many requests", TooManyRequestsError),

The second also covers the existing AUTHENTICATION_ERROR variant, and any future code the cloud attaches to the same message.

🧾 Environment

• pyoverkiz 2.1.0
• Hub: Atlantic Cozytouch V2 (io://****-****-9776), cloud API — local API not available for this server
• Seen on the events/{listener_id}/fetch endpoint, documented as "1 calls per 1 SECONDS period for this particular operation (polling)"

Happy to open a PR for whichever form you prefer.