CMC never recovers from burst limit cap

[boxhock]

We have seen on adapters in prod, staging and from [node op] that their CMC adapter is never able to recover from the burst limit cap: Minute Burst rate limit cap reached

The only fix here is to restart the adapter. It will continue spewing out error messages in the logs, but seemingly starts responding to requests again.

Does batching stop working due to a failing pair?

@Chainlink_Jonas - that might be fyi:
This seems to occur with a high number of jobs running through CMC. The requests in the warmup phase are too high and set the adapter in an error loop of IP rate limiting. Increasing the CacheMax Age then allows a "clean" start.
e.g: our adapter with proffessional tier only starts cleanly with CACHE_MAX_ITEMS=90000