🎇 Fix calendar.tsx typescript errors

[ansballard]

We were passing IconLeft and IconRight to the react-day-picker component, when those aren't actually options in the components prop. Per https://daypicker.dev/api/type-aliases/CustomComponents, it looks like what we should've used is PreviousMonthButton and NextMonthButton. Confirmed in a prod codespace editing calendar.tsx directly that this does render the correct icons.

This was the only tsc error that comes up when running npx tsc from the built-in components, so resolving issues with generated code should be easier without the noise

before	after

[Copilot]

Pull Request Overview

This PR fixes TypeScript errors in the calendar component by aligning the custom navigation button props with the react-day-picker API.

• Renamed IconLeft to PreviousMonthButton and IconRight to NextMonthButton in the components prop.
• Eliminates the sole remaining tsc error in built-in components.

Comments suppressed due to low confidence (2)

src/components/ui/calendar.tsx:62

• There are no existing tests covering custom month navigation buttons; consider adding unit or integration tests to verify that PreviousMonthButton and NextMonthButton render the correct icons and handle click events.

        PreviousMonthButton: ({ className, ...props }) => (

src/components/ui/calendar.tsx:62

• Add a code comment or update the component's docs to explain the change from IconLeft/IconRight to PreviousMonthButton/NextMonthButton, referencing the relevant react-day-picker API.

        PreviousMonthButton: ({ className, ...props }) => (

[justinmcbride]

Not the point of this PR, but am I crazy or are those day markers in your screenshots all wonky?

[ansballard]

Not the point of this PR, but am I crazy or are those day markers in your screenshots all wonky?

@justinmcbride They are, I've hit that a couple times but I haven't dug in to see if we need to add styles to the component or give the prompt a better stylistic nudge