RM-255: Re-enable force-disabled panels

[biast12]

Description

• When a free-tier server deletes a panel, ForceDisableSome is now called to re-enforce the 3-panel limit in both directions — if a slot opened up by deleting an active panel, the oldest force-disabled panel is automatically
  re-enabled to fill it
• When a premium server loads their panels and any are still force-disabled (e.g. from a previous subscription lapse), EnableAll is triggered at list time to restore them, and the response reflects the corrected state immediately
  without a second fetch

Needs: TicketsBot-cloud/database#36

Type of Change

• Bug fix
• New feature
• Breaking change

Testing

• Free tier server with 5 panels (3 active, 2 force-disabled): delete an active panel → one force-disabled panel becomes active
• Free tier server with 5 panels: delete a force-disabled panel → no state change
• Free tier server at exactly 3 active panels with no force-disabled: delete a panel → no spurious enables
• Premium server with force-disabled panels (simulated lapse): open the panels page → all panels re-enabled in the response

Checklist

• My code follows the style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[cloudflare-workers-and-pages]

Deploying tickets-v2-dashboard with    Cloudflare Pages

Latest commit:	ed8facb
Status:	✅  Deploy successful!
Preview URL:	https://91d4320f.tickets-v2-dashboard.pages.dev
Branch Preview URL:	https://rm-255.tickets-v2-dashboard.pages.dev

View logs

[BenHall-1]

@biast12 good to bump when you are

[biast12]

bumped!