feat: Introduce client management and integration updates

- Added client_id field to StoreTenantRequest and UpdateTenantRequest for tenant management.
- Updated TenantResource to include client_id in the response.
- Created migration to establish clients table and link tenants to clients.
- Migrated existing tenant integrations to client_integrations table.
- Grouped specific tenants under a shared client (OnTicket) in a new migration.
- Updated seeders to reflect new client structure and relationships.
- Adjusted integration configurations to require client instead of tenant.
- Added tests for client integration functionality and ensured existing tests reflect the new client structure.

lang/en/api.php

@@ -73,7 +73,7 @@ return [
         'scanner_category_forbidden' => 'The scanner is not assigned to the ticket category.',
     ],
     'integration' => [
-        'not_configured' => 'The integration is not configured for this tenant.',
+        'not_configured' => 'The integration is not configured for this client.',
         'configured' => 'Integration configured successfully.',
         'validation_failed' => 'Configuration validation failed: :error',
         'invalid_payment_method' => 'Invalid payment method.',

lang/es/api.php

@@ -73,7 +73,7 @@ return [
         'scanner_category_forbidden' => 'El scanner no está asignado a la categoría del ticket.',
     ],
     'integration' => [
-        'not_configured' => 'La integración no está configurada para este tenant.',
+        'not_configured' => 'La integración no está configurada para este cliente.',
         'configured' => 'Integración configurada correctamente.',
         'validation_failed' => 'Error validando la configuración: :error',
         'invalid_payment_method' => 'Método de pago inválido.',