Tell RobustHTTPClient to treat rate-limiting as non-retryable error (#439)
This is a simplest possible approach to pass through hitting a rate
limit to the application that uses the default XRPC client.
It's a design question if this is what you want to have. Alternatives
include:
* Gate this behaviour change behind a flag in `xrpc.Client` struct
* Allowing to specify a threshold for the duration until rate limit
reset, below which the client would keep the current behaviour
FWIW, JS client seems to not have any retry logic in place.