Add rate limit / throttling feedback for API usage

[maypole-degree]

Description:

When a user application exceeds API request limits (rate limits) while using the CDP SDK, the responses returned by the SDK or underlying API are not clearly annotated as rate-limit errors. As a result, developers cannot reliably detect a throttling situation and handle it (such as backing off or retrying after a delay). Instead, generic error messages are returned, which makes it difficult to distinguish between genuine errors and rate limit conditions.

Steps to reproduce:

1. Set up a project that uses the CDP SDK to make repeated requests to CDP endpoints.
2. Programmatically send a large number of requests in quick succession (e.g., in a loop or high-frequency polling).
3. Observe that at some point the server begins limiting requests (rate-limited).
4. Inspect the errors returned by the SDK or API client.
5. Notice that the error does not clearly indicate it was caused by rate limiting or throttling.