Patches to the rate limit parsing

The issue #356 comments on some incorrect logic when handling rate limits. Previously this would cause several requests to simply fail (say you're spamming reactions), this patch fixes that.

Note that there's still a bucket race, so the second request might use a old/invalid bucket, which can cause a temporary rate limit. This is being worked on.