Make bStats 429 Ratelimit errors less scary looking

[Bastian]

Currently, a huge stack trace is logged if a 429 Ratelimit errors is encountered (and logFailedRequests is enabled).

Since 429 are expected and are nearly guaranteed to happen once after server startup the error message should be shorter and explain that it is no problem.

[isiah-lloyd]

I agree, I was adding custom chars to my plugin and got the 429 error and assumed it was something wrong with my implementation.

[ChrissW-R1]

Please just set logFailedRequests to false. It's a debug option that was never intended to be enabled the whole time.

Thanks. This worked for us.