fix: Load type extensions via Update-TypeData to avoid conflicts

Use Update-TypeData -ErrorAction SilentlyContinue in the psm1
instead of TypesToProcess in the psd1. This prevents errors when
dbatools also loads its own identical type extensions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: potatoqualitee

dbatools.library.psd1

@@ -34,9 +34,6 @@
     # but only in Full .NET because Core does something different
     RequiredAssemblies     = @()
 
-    # Type files (.ps1xml) to be loaded when importing this module
-    TypesToProcess         = @('xml/dbatools.Types.ps1xml')
-
     # Script module or binary module file associated with this manifest.
     RootModule             = 'dbatools.library.psm1'
 

dbatools.library.psm1

@@ -339,4 +339,11 @@ if (Test-Path $dbatoolsDll) {
     } catch {
         Write-Error "Could not import dbatools binary module: $($_ | Out-String)"
     }
+}
+
+# Load type extensions (Query/Invoke on SMO Server/Database, serialization depth for exceptions)
+# Use -ErrorAction SilentlyContinue because dbatools may also load identical type data
+$typesFile = [IO.Path]::Combine($PSScriptRoot, "xml", "dbatools.Types.ps1xml")
+if (Test-Path $typesFile) {
+    Update-TypeData -PrependPath $typesFile -ErrorAction SilentlyContinue
 }