[Feature]: Expand VIP token automation and configuration

[Jamesllllllllll]

Problem or use case

Channels may want VIP token behavior that better matches subscriptions, gifting, donations, and queue-priority workflows. The current VIP token system is more limited than some streamers want.

Proposed solution

Expand VIP token automation and configuration with options such as:

• automating VIP token grants from donations
• granting tokens only to sub gifters
• granting tokens only to gift recipients
• allowing decimal places in VIP output for subscriptions
• optionally using !vip <request> as a queue bump system instead of the current VIP request model

Alternatives considered

Keep the current VIP token behavior fixed, but that does not cover the range of monetization and queue-management workflows channels may want.

Additional context

The optional bump-based VIP mode should be treated as a configurable alternative, not necessarily a replacement for the existing system.

[Jamesllllllllll]

Current status for #18:

• Merged PR Release 0.1.1 VIP token automation and bot auth improvements #35 delivered the core VIP token work: fractional balances, gifted-sub and cheer automation, public playlist messaging, and the related dashboard settings.
• Open PR Allow upgrading existing requests between regular and VIP #37 builds on that by making existing requests easier to convert between regular and VIP without creating duplicates.

What PR #37 adds:

• !vip <existing request> now upgrades a viewer's matching regular request in place instead of adding a duplicate.
• !sr <existing VIP request> now downgrades that request back to regular and refunds the VIP token.
• Bot replies for those conversions now explicitly say when a VIP token was used or refunded.
• The dashboard playlist manager can now do the same regular <-> VIP conversion from the UI, using the same token consume/refund rules and queueing the same style of bot confirmation reply.
• The public playlist search total fix is included in the same follow-up.

Still open under #18:

• off-platform donation integrations (StreamElements / Streamlabs / PayPal-style providers)
• any broader VIP policy expansion beyond the Twitch-native automation and request conversion flows

Important limitation that still applies:

• Twitch alone cannot detect generic off-platform donations, so donation-based VIP token grants require direct integrations with those providers or a manual admin workflow.

Links:

• PR Release 0.1.1 VIP token automation and bot auth improvements #35: Release 0.1.1 VIP token automation and bot auth improvements #35
• PR Allow upgrading existing requests between regular and VIP #37: Allow upgrading existing requests between regular and VIP #37

[Jamesllllllllll]

Opened #42 to cover the broader product-design side of VIP/premium request behavior.

#18 should stay focused on automation/configuration work, while #42 captures the wider questions around:

• subscriber renewal rewards
• passive queue-slot perks
• duration-based premium request rules
• surfacing "requires VIP token" / "requires donation" messaging in search and playlist UX

[Jamesllllllllll]

Additional notes from observed current streamer workflows:

• streamers may want VIP token grants to vary by sub tier rather than using one flat subscription reward
• a common example shape is 1 token for a base sub or gifted sub, 2 for a tier 2 sub, and 5 for a tier 3 sub
• a simple bits conversion is also common, for example a fixed bits-per-token rule such as 500 bits for 1 token
• this issue should keep room for clear per-source reward rules instead of assuming one uniform subscription reward path