Update shadcn/ui components in the design package #761

Description

The shared design package contains shadcn/ui-derived components under packages/design/src/components. These components should be reviewed against the current shadcn/ui guidance and updated intentionally so Lucky Parking stays aligned with upstream accessibility, dependency, Tailwind, and component API improvements while preserving our project-specific design decisions.

Action Items

• Review the current shadcn/ui changelog and release notes for changes relevant to the components currently copied into packages/design.
• Audit packages/design/src/components.json, component files, hooks, utilities, CSS, and package dependencies for drift from current shadcn/ui recommendations.
• Identify which existing components should be regenerated, manually updated, or intentionally left customized.
• Update the affected design package components and dependencies, preserving Lucky Parking-specific styling and exported APIs where appropriate.
• Confirm downstream imports in apps/web still work after the update.
• Run the relevant verification commands for formatting, linting, type checking, build, and available tests.
• Document any intentional deviations from upstream shadcn/ui patterns in the PR description or design package notes.

Additional Information

Relevant repo paths:

• packages/design/src/components.json
• packages/design/src/components
• packages/design/src/hooks
• packages/design/src/lib/utils.ts
• packages/design/src/css
• packages/design/package.json
• apps/web

Relevant references:

• shadcn/ui changelog: https://ui.shadcn.com/docs/changelog
• shadcn/ui releases: https://github.com/shadcn-ui/ui/releases
• shadcn/ui installation / CLI guidance: https://ui.shadcn.com/docs/installation#use-create
• Vercel Academy: Updating and Maintaining Components: https://vercel.com/academy/shadcn-ui/updating-and-maintaining-components

Notes:

• shadcn/ui components are copied into the repo, so this should not be treated as a normal dependency-only upgrade.
• Avoid replacing local customizations blindly. Compare upstream behavior against existing Lucky Parking usage before changing public component APIs.
• If the update reveals larger design-system decisions, capture those as follow-up issues instead of expanding this task indefinitely.