output to log when detecting incorrect rate limiters

[andersfylling]

todo:

1. check if the expected stored rate limit info is incorrect when receiving a response

issues:

1. This is concurrent programming, remember to lock the bucket.

when the current values, requests left before rate limited, subtracted by one does not match the rate limits in the header response; output to log, the url + bucket key.

[andersfylling]

Given that people might setup different instances of their bots, this can cause more confusion than it solves as it might spew out data all the time.

Closed unless someone can counter my reasoning.