fix: 429 error not shown

[Toricane]

About

This pull request shows the 429 error properly.

I've been seeing lots of JSONDecodeErrors from mostly Replit users (there is a documented case of it happening with Heroku as well), which leads to a TypeError. The common "fix" given to them was just to do kill 1 in the shell with no additional information as to what happened and why.

When I looked further into the code, I saw that when Cloudflare ratelimits you, it returns an HTML page instead of JSON, causing the JSONDecodeError (because the library tries to JSONify the response immediately without any checks), which is typical for Replit users. The suggestion of kill 1 basically runs the code on a new server in Replit, sometimes with a new IP, so it temporarily works again.

Ideally, this error shouldn't occur at all because the library handles ratelimits awesomely, but when it does occur, it isn't handled properly.

This PR highlights that it is a 429 error instead of not handling the exception.

Checklist

• The pre-commit code linter has been run over all edited files to ensure the code is linted.
• I've ensured the change(s) work on 3.8.6 and higher.

I've made this pull request: (check all that apply)

• For the documentation
• To add a new feature
• As a general enhancement
• As a refactor of the library/the library's code
• To fix an existing bug
• To resolve #ISSUENUMBER

This is:

• A breaking change

[Toricane]

@EdVraz ready for review

[EepyElvyra]

Lgtm I think