feat: Add time-of-day filtering with quick hour filters and time range picker

[Yashh56]

This pull request adds enhanced time-based filtering options to the DateFilter component, allowing users to select more granular time ranges, including specific hours within a day. It introduces a new TimeRangePickerForm component, updates the available filter options, and adds supporting labels for improved user experience.

New time range filtering features:

• Added a new TimeRangePickerForm component that allows users to select a specific date and start/end hours, enabling hour-level granularity for date filters. (src/components/metrics/TimeRangePickerForm.tsx)
• Updated the DateFilter component to include new quick-select options for the last 1, 2, 4, 6, and 12 hours, and added a "Time range" option that opens the new time picker modal. (src/components/input/DateFilter.tsx) [1] [2]
• Integrated the new time range picker modal into the DateFilter component, handling its open/close state and passing selected values back to the parent. (src/components/input/DateFilter.tsx) [1] [2] [3] [4]

Internationalization and UI improvements:

• Added new message labels for "Time range", "Start time", and "End time" to support the new filtering options. (src/components/messages.ts)
• Imported the new TimeRangePickerForm in the DateFilter component to enable the modal functionality. (src/components/input/DateFilter.tsx)

Closes #3962

[vercel]

@Yashh56 is attempting to deploy a commit to the umami-software Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

This PR enhances the DateFilter component with five new quick-select hour options (1 h, 2 h, 4 h, 6 h, 12 h) and a custom "Time range" picker that lets users select a specific calendar date plus a start/end hour, emitting the result in the existing range:<startMs>:<endMs> format that the rest of the codebase already parses correctly.

The previously flagged issues (duplicate export const labels, missing defineMessages import, formatMessage calls that would throw at runtime, and uninitialized hour state) have all been resolved in this revision. One remaining issue:

• Missing locale translations (P1) — The three new label keys (label.time-range, label.start-time, label.end-time) are defined in messages.ts but not present in any locale file (including public/intl/messages/en-US.json). next-intl will render the raw key string verbatim for all users until the translations are added.

Confidence Score: 4/5

Safe to merge once the missing locale translation strings are added; all previously flagged runtime errors are resolved.

All major prior issues (formatMessage crash, duplicate labels declaration, uninitialized state) are fixed. The one remaining P1 is missing translation entries in locale files — the new UI elements will render raw key strings (e.g. "label.time-range") for every user until the strings are added.

public/intl/messages/en-US.json (and other locale files) need the three new translation keys added.

Important Files Changed

Filename	Overview
src/components/metrics/TimeRangePickerForm.tsx	New time-range picker component; logic and hook usage are correct, but the translation keys it references are missing from locale files.
src/components/input/DateFilter.tsx	Adds 1/2/4/6/12-hour quick filters and a Time Range modal trigger; references label.timeRange which has no locale translation yet.
src/components/messages.ts	New keys timeRange, startTime, endTime correctly appended to the existing labels Record; no structural issues.

_{Reviews (5): Last reviewed commit: "Use translation function for time range ..." | Re-trigger Greptile}

[greptile-apps]

_{3 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[Yashh56]

@greptileai

[greptile-apps]

_{No files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[Yashh56]

@greptileai

[Yashh56]

@greptileai

[Yashh56]

@greptileai

[Yashh56]

Hey @mikecao , can you please have a look at this?