Update route.ts

Refactor incoming message handling: Added early check for WhatsApp number activity to skip processing for inactive numbers. Retained previous check for redundancy and safety, enhancing overall message handling efficiency.

Implement active status check for WhatsApp number before sending messages: Added logic to verify if the WhatsApp number is active, preventing message sending for inactive numbers. This enhancement improves message handling and user experience by ensuring only valid numbers are processed.

Refactor WhatsApp number handling in ClientsPage: Updated client_id assignments to use null instead of undefined for better database compatibility. Enhanced data retrieval with .maybeSingle() to handle cases with no returned rows, ensuring robust updates to WhatsApp numbers and client associations.

Refactor ClientsPage: Removed active status toggle functionality and associated UI elements for clients. This change simplifies the client management interface by eliminating the ability to activate or deactivate clients directly from the dashboard.

Update WhatsApp number management: Refined active status handling by incorporating the force_inactive property across various components. Adjusted UI elements to accurately reflect the active/inactive state based on both is_active and force_inactive flags, ensuring consistent user experience and status representation.

Enhance WhatsApp number management: Updated active status logic to exclude numbers marked as force_inactive. Modified API responses and UI components to reflect the new force_inactive property, ensuring accurate representation of WhatsApp number statuses across the application.

Implement immediate active status update for WhatsApp numbers: Added functionality to toggle the active status of WhatsApp numbers and update the database in real-time. Enhanced error handling to revert UI state on update failure and provide user feedback through toast notifications.

Add client update functionality and active status toggle: Implemented a PUT API endpoint for updating client details, including name, email, and active status. Enhanced ClientsPage to support client status toggling and improved error handling for updates.

Enhance GreenApiClient configuration: Added 'Accept' header and enabled response decompression for axios requests, improving compatibility and performance for message and file uploads.

Remove deprecated GreenAPI example functions: Deleted the green-api-example.ts file, which contained example functions for sending messages and images using GreenAPI with both default and specific credentials. This cleanup helps streamline the codebase by removing unused examples.

Refactor client addition in ClientsPage: Transitioned to using a server-side API for client creation, improving error handling and ensuring the clients list updates correctly upon successful addition.

Refactor client addition logic in ClientsPage: Updated the process to utilize a server-side API for client creation, enhancing error handling and ensuring the clients list updates correctly upon successful addition.

Refactor client creation process in ClientsPage: Updated the client addition logic to utilize a server-side API endpoint instead of directly creating users with Supabase. Improved error handling for client creation and streamlined the process of updating the clients list upon successful addition.

Implement webhook authorization check and refine axios configuration: Added logic to validate the webhook-authorization header for GreenAPI, enhancing security. Updated axios requests in GreenApiClient to use a more structured configuration, improving error handling and timeout settings for message and file uploads.