Show what's being rolled back in the rollback confirmation

[acoshift]

Summary

The deployment rollback confirmation was a bare title ("Rollback web to revision 6") — it never told the user what that revision actually contains. This replaces it with an in-page modal that spells it out:

• Currently active vs Rolling back to, side by side: revision number, image ref, deploy time, and author.
• A note that rollback redeploys the target revision's image and configuration (env, scaling, command) as a new revision, and that no history is deleted — matching what deployment.rollback actually does server-side (it re-Deploys the target's full spec).
• Built as an in-page modal (per the repo's modal convention) rather than SweetAlert html, so user-provided image refs render through Svelte interpolation; backdrop-click close uses the existing e.target === e.currentTarget pattern, and closing is blocked while the rollback request is in flight.

bun lint + bun check: 0 errors. Verified against bun dev:mock with Playwright:

before	after
SweetAlert title only	side-by-side revision comparison

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying deploys-app--console with    Cloudflare Pages

Latest commit:	bd5968b
Status:	✅  Deploy successful!
Preview URL:	https://e3ea4111.deploys-app--console.pages.dev
Branch Preview URL:	https://rollback-modal-detail.deploys-app--console.pages.dev

View logs

[acoshift]

Rechecked the copy against the apiserver (server/deployment.go Rollback): it re-Deploys the target revision's image, env (+ groups), min/max replicas, type, port, command/args, workload identity, pull secret, disks, schedule, and resources — but passes no Sidecars/MountData/TTL, which Deploy treats as "keep current". cd73a5f updates the modal note accordingly: "…(env, scaling, command, disks, schedule)… Sidecars and mounted files keep their current configuration."

[acoshift]

Follow-up: the modal is now wider (56rem, scrolls when long, cards stack on mobile) and fetches the target revision's full spec via deployment.get { revision } to show a configuration diff — settings rows (scaling, port, schedule, command, args, env groups, workload identity, pull secret, disk, memory) plus a per-key env diff with +/−/± badges, current vs after-rollback. Loading/failure/no-changes states included; mock deployment.get now honors revision so the diff renders in offline dev.