[Docs] QStash rate limiting needs documentation

[miketromba]

For a service as essential and critical as a message queue, any/all rate limiting logic should be completely transparent for end users to design their systems around. Because of the lack documentation on this, I ran with the assumption that there were no rate limits (within the bounds of the plan I'm paying for) and I engineered my system around that assumption.

However, in production, I'm now seeing response headers like this:

Burst-Ratelimit-Limit: 150
Burst-Ratelimit-Remaining: 149
Burst-Ratelimit-Reset: 1692222232

Uhh...

I'm using Upstash as the message queue for my email marketing SaaS. My backend is designed to enqueue thousands of sendEmail messages at once and consume thousands of open/click tracking events in very sharp bursts. It would have been great to be aware of this up front while designing my system.

Please document rate limiting in detail so engineers can plan ahead! :)

[miketromba]

Closing because it appears that either:

a) I missed this information when reading through the pricing page while building my system or b) It just recently got added to the pricing page / changed since I first built my system

Either way, this issue is irrelevant now. Oops.