feat: comply with undocumented helix rate limits

[iProdigy]

Prerequisites for Code Changes

• This pull request follows the code style of the project
• I have tested this feature

Issues Fixed

• Prevents 429's from some helix endpoints with special undocumented rate limits
• Prevents 429's from consistently hammering (general) helix endpoints (due to refill rate asymmetry)

Changes Proposed

• Restrict banUser/unbanUser calls to 100/30 bucket per channel
• Restrict addBlockedTerm/removeBlockedTerm calls to 60/60 bucket per channel
• Restrict createClip calls to 600/60 bucket per user
• Reduce helix bucket refill rate to 600/60
• Allow users to override the global helix ratelimit (to be less than 800/60, for example)
• Fix resource leak in error decoders

[PhilippHeuer]

Good job - and great investigation on the 429's :)