refactor: move data-table hooks/contexts/provider from features to web modules

[eunjae-lee]

What does this PR do?

Moves client-side data-table code (React hooks, contexts, DataTableProvider) from packages/features/data-table/ to apps/web/modules/data-table/, per the vertical slice architecture rule that packages/features should only contain framework-agnostic code.

Recreates the work from the closed #27228, rebased on top of the recent data-table refactors.

Moved to apps/web/modules/data-table/:

• hooks/ (12 files) — all React hooks (useDataTable, useColumnFilters, useFilterValue, etc.)
• contexts/ (4 files) — DataTableFiltersContext, DataTableSegmentContext, DataTableStateContext
• DataTableProvider.tsx

Stays in packages/features/data-table/:

• lib/ — types, utils, serializers, parsers, dateRange
• repositories/ — filterSegment data access
• __tests__/, GUIDE.md
• index.ts — trimmed to only re-export lib/types, lib/utils, lib/serializers, lib/separator

Import updates (~40 consumer files):

• Types/utils (ColumnFilterType, ZFilterValue, convertFacetedValuesToMap, etc.) continue importing from @calcom/features/data-table
• Hooks/contexts/provider now import from ~/data-table/... paths

GUIDE.md updates:

• Updated Quick Start import examples to show the split between @calcom/features/data-table (types/utils) and ~/data-table/... (hooks/provider/components)
• Fixed file path references that pointed to old packages/features/ locations
• Updated closing section to list both source locations

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A — GUIDE.md within the package was updated to reflect new import paths.
• I confirm automated tests are in place that prove my fix is effective or that my feature works. N/A — refactor only, existing tests cover functionality.

How should this be tested?

1. Run yarn type-check:ci --force — should pass (pre-existing embed-react errors are unrelated)
2. Run yarn lint — should pass with only pre-existing warnings
3. Verify data tables render correctly in:
   • Bookings page
   • Insights pages
   • User list tables
   • Out of office entries

Checklist

• My code follows the style guidelines of this project
• I haven't checked if my changes generate no new warnings

Human Review Checklist

• Verify the ActiveFiltersValidator type import in useActiveFiltersValidator.ts — it now imports from ~/data-table/DataTableProvider instead of the barrel @calcom/features/data-table, since this type was defined in the contexts that moved
• Verify no consumers in packages/ were missed that import hooks/contexts from the old barrel export (CI type-check passed, but worth a quick scan)
• Verify GUIDE.md import examples accurately reflect the new split

---

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

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

Devin AI is resolving merge conflicts

This PR has merge conflicts with the main branch. A Devin session has been created to automatically resolve them.

View Devin Session

Devin will:

1. Merge the latest main into this branch
2. Resolve any conflicts intelligently
3. Run lint/type checks to ensure validity
4. Push the resolved changes

If you prefer to resolve conflicts manually, you can close the Devin session and handle it yourself.

[devin-ai-integration]

Merge conflicts with main have been resolved and pushed. All 7 conflicting files were import-only conflicts where the PR's moved imports (~/data-table/...) needed to be reconciled with main's formatting changes. The resolution preserves the PR's intent (hooks/contexts/provider imported from ~/data-table/...) while adopting main's multi-line import formatting.

• Type check passes (only pre-existing embed-react errors)
• Lint passes (only pre-existing warnings)
• Merge commit file count: 63 (matches original PR)

Note: Unable to remove the devin-conflict-resolution label automatically due to API auth limitations — please remove it manually.

[github-actions]

E2E results are ready!

• Workflow #104299.1 latest results

[hbjORbj]

Nice, thanks Eunjae!