Limits of Laravel Jetstream's Profile Form Regarding Timezone Selection

Goal

Allow each user to select a preferred timezone so that timestamps shown in the Jetstream interface reflect their local time rather than a single application‑wide setting.

Uncertainty

Jetstream’s default profile update form does not include a timezone field, leaving developers to decide whether to add a manual dropdown, rely on browser‑detected timezone via JavaScript, or combine both approaches, and how to validate the stored value to prevent Carbon instantiation errors.

Should Jetstream provide a built‑in timezone selector in the profile update form? Should the selector use browser detection, a manual list, or both? What validation rules should be applied to the stored timezone string?