Manage 429 RateLimit Errors with Spring WebClient

The project was using an outdated synchronous RestTemplate client instead of the newer Spring WebClient, which is built on top of Reactor API. The error log showed a 429 Too Many Requests error with a 1-minute rate limit. After converting to the new WebClient, it's possible to extract the Retry-After header from the response and implement retry strategies using Reactor's Retries mechanism.