Get-DbaCmObject - Apply CimOperationTimeout config to all CIM connections

Ensures CimWinRMOptions and CimDCOMOptions are initialized with the
ComputerManagement.CimOperationTimeout config value (default: 60s) whenever
Get-DbaCmObject retrieves a connection, not only when New-DbaCmConnection or
Set-DbaCmConnection are explicitly called. This prevents indefinite hangs when
querying servers with hung or corrupted WMI.

Fixes #6498

Co-authored-by: Andreas Jordan <andreasjordan@users.noreply.github.com>

Author: github-actions[bot]

public/Get-DbaCmObject.ps1

@@ -255,6 +255,14 @@ function Get-DbaCmObject {
 
             $connection = $connectionObject.Connection
 
+            # Ensure CIM session options are initialized with the configured operation timeout
+            if ($null -eq $connection.CimWinRMOptions) {
+                $connection.CimWinRMOptions = New-DbaCimSessionOptionWithTimeout -Protocol Default
+            }
+            if ($null -eq $connection.CimDCOMOptions) {
+                $connection.CimDCOMOptions = New-DbaCimSessionOptionWithTimeout -Protocol Dcom
+            }
+
             # Ensure using the right credentials
             try { $cred = $connection.GetCredential($Credential) }
             catch {