Refactor vCenter snapshot handling and VM operations

- Introduced a new method `resolveVCenterFromProduct` in `SnapshotService` to streamline vCenter resolution from product data.
- Updated `CreateSnapshot`, `RemoveSnapshot`, and `RevertSnapshot` jobs to utilize the new vCenter resolution method.
- Enhanced the `VmController` to support UUID-based service identification for VM operations.
- Added new actions for changing VM IP and RDP port, encapsulating the logic for these operations.
- Improved error handling and logging for VM operations, including detailed responses for API consumers.
- Removed unnecessary relationships in model queries to optimize performance.

app/Http/Services/vCenter/SnapshotService.php

@@ -17,19 +17,54 @@ class SnapshotService
         $this->powerShellService = $powerShellService;
     }
 
+    /**
+     * Resolve vCenter từ product (ModuleVmware) qua nhiều cách:
+     * 1. Direct relation qua vcenter_id
+     * 2. Qua ipAddress → host → datacenter → vCenter
+     * 3. Qua Service relation
+     */
+    protected function resolveVCenterFromProduct($product): ?\App\Models\vCenter
+    {
+        // Cách 1: Ưu tiên quan hệ trực tiếp trên ModuleVmware
+        if ($product->vCenter) {
+            return $product->vCenter;
+        }
+
+        // Cách 2: Fallback qua ipAddress chain
+        if ($product->ipaddress?->host?->datacenter?->vCenter) {
+            return $product->ipaddress->host->datacenter->vCenter;
+        }
+
+        // Cách 3: Qua Service relation
+        $service = $product->services()->first();
+        if ($service) {
+            $service->load('vmware.vCenter');
+            if ($service->vmware?->vCenter) {
+                return $service->vmware->vCenter;
+            }
+        }
+
+        return null;
+    }
+
     public function CreateSnapShot($product): string|array
     {
         try {
             // Note: credentials setup logic from original vCenter.php seemed redundant with Client logic,
-            // but CreateSnapShot was overwriting $this->username/password. 
+            // but CreateSnapShot was overwriting $this->username/password.
             // Here we assume Client is used, or we need to update Client.
             // Client stores token. If we need username/password for something else, Client has them now via getters.
             // But CreateSnapshot used $product->ipaddress...->vCenter->user/password.
-            
+
             // Re-login to ensure we have the right credentials for the vCenter associated with the product
-            $vcenterModel = $product->ipaddress->host->datacenter->vCenter;
+            $vcenterModel = $this->resolveVCenterFromProduct($product);
+
+            if (!$vcenterModel) {
+                return ['error' => true, 'message' => 'Không tìm thấy thông tin vCenter cho VM'];
+            }
+
             $this->client->loginServer($vcenterModel);
-            
+
         } catch (\Exception $e) {
             return ['error' => true, 'message' => 'Lỗi setup credentials: ' . $e->getMessage()];
         }
@@ -86,7 +121,12 @@ class SnapshotService
         // and add the private helpers it depends on.
         
         try {
-            $vcenterModel = $product->ipaddress->host->datacenter->vCenter;
+            $vcenterModel = $this->resolveVCenterFromProduct($product);
+
+            if (!$vcenterModel) {
+                return ['error' => true, 'message' => 'Không tìm thấy thông tin vCenter cho VM'];
+            }
+
             $this->client->loginServer($vcenterModel);
         } catch (\Exception $e) {
             return ['error' => true, 'message' => 'Lỗi setup credentials: ' . $e->getMessage()];