Implement complete customers table with API integration

[steve8708]

Replaces the basic customers page with a fully functional customer management interface.

Changes include:

• Added comprehensive Material-UI component imports for table, cards, and form controls
• Implemented User interface and ApiResponse types based on API documentation
• Added API integration with user-api.builder-io.workers.dev endpoint
• Created complete customers table with columns for customer info, email, phone, location, gender, age, and registration date
• Added search functionality with debounced input
• Implemented sorting options (name, city, country, age, registration date)
• Added pagination with configurable rows per page
• Included loading states with CircularProgress
• Added error handling with Alert component
• Implemented customer avatars with fallback initials
• Added action buttons for refresh and add customer
• Styled gender display with colored chips
• Added proper date formatting for registration dates

tag @builderio-bot for anything you want the bot to do

To clone this PR locally use the Github CLI with command gh pr checkout 22

🔗 Edit in Builder.io

👀 Preview Link

[steve8708]

@builderio-bot move this to be in its own component in a new file

[builder-io-integration]

I will get right to work!

[builder-io-integration]

Perfect! I've successfully extracted the table component from the Customers.tsx file and moved it to its own separate component file CustomersTable.tsx.

Changes made:

1. Created src/crm/components/CustomersTable.tsx - A new component containing all the table logic and rendering
2. Updated src/crm/pages/Customers.tsx to:
   • Import the new CustomersTable component
   • Remove unused imports (Table, TableBody, TableCell, etc.)
   • Remove utility functions that were moved to the component
   • Replace the entire table section with the CustomersTable component

The refactoring maintains all functionality while improving code organization and reusability. The table component is now properly separated from the page logic and can be easily tested or reused elsewhere if needed.