Show Discord integration to Ultra subscribers; rename role to "Ultra"

[simonhamp]

Summary

• The Discord integration banner on the customer integrations page was gated behind hasMaxAccess(), which only covers perpetual Max licenses. Ultra subscribers (hasUltraAccess()) couldn't see or claim the role even though they qualify. This widens the gate across all five sites involved in the role lifecycle: the integrations page, the OAuth callback, AssignDiscordUltraRoleJob, the requestUltraRole() Livewire action, the discord:remove-expired-roles command, and the Stripe cancellation cleanup in StripeWebhookReceivedListener.
• Renames the role end-to-end from "Max" to "Ultra" to match the new branding — config key (services.discord.max_role_id → ultra_role_id), env var (DISCORD_MAX_ROLE_ID → DISCORD_ULTRA_ROLE_ID), DiscordApi methods (assignMaxRole/removeMaxRole/hasMaxRole → …UltraRole), job class names, Livewire state and action, and all user-facing copy. The Discord role ID itself doesn't change — only the variable name and the role's display name (to be renamed in Discord manually).
• Adds tests/Feature/DiscordUltraAccessTest.php covering banner visibility, role request happy/rejection paths, and the cleanup command's retain/remove behavior under the new rule.

Deployment note

The env var DISCORD_MAX_ROLE_ID must be renamed to DISCORD_ULTRA_ROLE_ID in any staging/production environment that has it set. The Discord role's display name should also be updated in the Discord server.

Test plan

• php artisan test --compact tests/Feature/DiscordUltraAccessTest.php — 6 passed
• php artisan test --compact tests/Feature/StripeWebhookRouteTest.php — 2 passed
• vendor/bin/pint --dirty --format agent — clean
• Manually verify an Ultra subscriber sees the Discord banner and can claim the role
• Manually verify a free user does not see the Discord banner

🤖 Generated with Claude Code