feat(dashboard): a registrations section for an event

[harshtandiya]

Stacked on version-2-dashboard-events-guests.

Adds a Registrations section to the event workspace: two status tiles that
gate signup, and the ticket tiers the event sells.

Registration has no boolean behind it. Buzz Event only has
registrations_close_at, and are_registrations_closed() already derives
open/closed from it for the booking flow. So the toggle writes the cutoff:
off is now in the event's own timezone, on clears it. Consequence worth
knowing: an event that has already ended still reads Closed after
reopening — same answer the public page gives, so it is honest, not a bug.
If we want a real flag later, that is a doctype change plus booking-flow
work, not this PR.

Guest registration carries guest_verification_method in the same
dialog, since neither field means much without the other.

Ticket tiers read and insert straight through useList — they inherit
their event's team scope from the permission hooks, so no endpoint. Creation
only. Edit, delete and publish stay in Desk for now, and tickets_sold /
remaining_tickets are Python properties a list call cannot fetch, so rows
show title and price and nothing else.

No new endpoint anywhere. get_event grew four fields; writes go through
the frappe.client.set_value resource the details page already uses.

Also here: nowInZone in utils/timeZones.ts (Frappe's naive datetime, in
the event's zone) and the first Switch usage in this dashboard.

Checked: 40 buzz.api.events tests, 18 timeZones unit tests, typecheck,
pre-commit, and the chromium e2e project. One pre-existing failure there,
auth.spec.ts › should login via UI, which fails on a stashed tree too.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

The PR adds an event registrations management section with registration and guest-booking controls plus ticket-tier creation.

• Extends event details with registration and guest-booking state.
• Adds registration settings dialogs and ticket-type listing and creation.
• Adds the management route, navigation entry, timezone utility, and end-to-end coverage.

Confidence Score: 3/5

The PR does not appear safe to merge until registration closing uses the same timezone fallback semantics as backend enforcement.

Timezone-less events still persist the organizer browser’s wall clock while the backend evaluates the cutoff in the server timezone, and unresolvable event zones still silently persist the browser wall clock, so registration can remain open or close earlier than requested.

Files Needing Attention: dashboard/src/utils/timeZones.ts, dashboard/src/components/dashboard/events/EventRegistrationDialog.vue

Important Files Changed

Filename	Overview
dashboard/src/utils/timeZones.ts	Adds event-zone wall-clock formatting, but its null and error fallbacks still produce cutoffs in the browser timezone rather than the timezone used by backend registration enforcement.
dashboard/src/components/dashboard/events/EventRegistrationDialog.vue	Adds registration open/close persistence and directly stores the timezone utility’s naive datetime result.
dashboard/src/pages/manage/events/EventRegistrations.vue	Adds the registrations workspace, status controls, and ticket-tier list while forwarding the event’s nullable timezone to the cutoff dialog.
buzz/api/events/services.py	Extends managed-event details with registration and guest-booking fields and derives the current registration status.
dashboard/src/components/dashboard/events/GuestRegistrationDialog.vue	Adds coordinated controls for guest booking and its optional verification method.
dashboard/src/components/dashboard/events/TicketTypeDialog.vue	Adds validated creation of event ticket tiers with price, currency, and optional capacity.
dashboard/src/data/tickets.ts	Adds scoped ticket-type and enabled-currency list resources.
dashboard/src/router.ts	Registers the static event registrations route before the dynamic management fallback.

_{Reviews (11): Last reviewed commit: "test(e2e): drive the registrations secti..." | Re-trigger Greptile}

[greptile-apps]

Fallback shifts registration cutoff

When an event contains an invalid, obsolete, or browser-unsupported timezone, nowInZone falls back to the organizer's browser timezone. The backend then interprets that naive timestamp in the event timezone, causing registration to close earlier or later than requested.

Knowledge Base Used:

• Events domain
• Public booking flow

Prompt To Fix With AI

This is a comment left during a code review.
Path: dashboard/src/utils/timeZones.ts
Line: 52-56

Comment:
**Fallback shifts registration cutoff**

When an event contains an invalid, obsolete, or browser-unsupported timezone, `nowInZone` falls back to the organizer's browser timezone. The backend then interprets that naive timestamp in the event timezone, causing registration to close earlier or later than requested.

**Knowledge Base Used:**
- [Events domain](https://app.greptile.com/bwh-tech/-/custom-context/knowledge-base/bwhtech/buzz/-/docs/events-domain.md)
- [Public booking flow](https://app.greptile.com/bwh-tech/-/custom-context/knowledge-base/bwhtech/buzz/-/docs/booking-flow.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[github-actions]

❌ UI Demo Check failed

This pull request changes the UI (11 file(s) under dashboard/src/),
but the description has no screenshot or demo. Reviewers should be able to see the
change without checking out the branch.

🛠️ How to fix

• Edit the description and drag a screenshot or a short screen recording into it.
  Before/after images are ideal for visual tweaks.
• Or apply the skip-demo label if a visual makes no sense here
  (pure refactor, copy change, dependency bump).

Either one re-runs this check automatically.