feat: implement default filter segments for data tables

Summary

This PR implements default filter segments for Cal.com's data table system, allowing users to access pre-defined filter combinations like "My Bookings" and "Upcoming Bookings" without having to create them manually. The implementation supports mixed segment ID types (numeric for user segments, string for default segments) and uses a dual database column approach for preference storage.

Key Changes:

• Database: Added defaultSegmentId VARCHAR column to UserFilterSegmentPreference table with constraints ensuring only one segment type per preference
• Type System: Introduced DefaultFilterSegment type and CombinedFilterSegment union type to handle mixed ID types throughout the application
• Core Logic: Updated useSegments hook, DataTableProvider, and repository methods to handle both user and default segments
• UI: Modified FilterSegmentSelect to group default segments separately with icons, and prevent editing/deleting of default segments
• Implementation: Added "My Bookings" and "Upcoming Bookings" default segments to the bookings view

Review & Testing Checklist for Human

• Test mixed segment ID functionality: Switch between user-created segments (numeric IDs) and default segments (string IDs) to ensure state management works correctly across URL changes and component re-renders
• Verify database migration: Check that the new defaultSegmentId column and constraints were applied correctly, and that existing user preferences still work
• Test default segment UI grouping: Confirm default segments appear first in dropdown with proper icons, have no submenu actions, and are visually distinguished from user segments
• Validate date range filters: Test "Upcoming Bookings" default segment to ensure the relative date range preset works correctly and updates dynamically
• Test segment preference persistence: Verify that selecting default segments saves preferences correctly and persists across page reloads

Recommended Test Plan:

1. Navigate to bookings page and verify default segments appear in filter dropdown
2. Select "My Bookings" and confirm it filters to current user's bookings
3. Select "Upcoming Bookings" and verify it shows future bookings only
4. Create a custom user segment and verify it appears in "Personal" group
5. Switch between default and user segments multiple times
6. Reload page and confirm last selected segment is remembered
7. Try to edit/delete a default segment (should be prevented)

Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    BookingsView["apps/web/modules/bookings/views/<br/>bookings-listing-view.tsx"]:::major-edit
    DataTableProvider["packages/features/data-table/<br/>DataTableProvider.tsx"]:::major-edit
    useSegments["packages/features/data-table/hooks/<br/>useSegments.ts"]:::major-edit
    FilterSegmentSelect["packages/features/data-table/components/<br/>segment/FilterSegmentSelect.tsx"]:::major-edit
    SaveSegmentButton["packages/features/data-table/components/<br/>segment/SaveFilterSegmentButton.tsx"]:::minor-edit
    Types["packages/features/data-table/<br/>lib/types.ts"]:::major-edit
    Repository["packages/lib/server/repository/<br/>filterSegment.ts"]:::major-edit
    Schema["packages/prisma/<br/>schema.prisma"]:::minor-edit
    Migration["packages/prisma/migrations/<br/>add_default_segment_id/"]:::major-edit

    BookingsView -->|"defines default segments"| DataTableProvider
    DataTableProvider -->|"passes defaultSegments prop"| useSegments
    useSegments -->|"combines user + default segments"| FilterSegmentSelect
    FilterSegmentSelect -->|"groups and displays segments"| SaveSegmentButton
    Types -->|"defines CombinedFilterSegment"| useSegments
    Types -->|"defines DefaultFilterSegment"| BookingsView
    Repository -->|"handles mixed ID types"| useSegments
    Schema -->|"adds defaultSegmentId column"| Migration
    Migration -->|"database schema change"| Repository

    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit
        L3[Context/No Edit]:::context
    end

    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF

Notes

• Mixed ID Type Complexity: The most critical aspect to review is the handling of mixed segment ID types (number vs string) throughout the data flow. This required updates to URL parsing, state management, database queries, and UI components.

• Frontend-Only Approach: Default segments are defined in component code rather than stored in the database, making them easier to deploy but requiring careful coordination between different views.

• Date Range Recalculation: Default segments with relative date ranges (like "upcoming") are recalculated on each render to stay current, which should be monitored for performance impact.

• Backward Compatibility: Existing user segments and preferences should continue working unchanged due to the dual-column database approach.

Link to Devin run: https://app.devin.ai/sessions/1c959909a25541de82f2ac0612e08a75
Requested by: @eunjae-lee