fix: correct Intune policy matching in drift report to avoid null-name false match

Get-CIPPDrift compared raw .displayName/.name properties across four OR
clauses to detect whether a tenant's Intune policy was already covered by
a template. Most Intune policy types (compliance policies, device
configurations, app protection policies, group policy configurations,
Windows Update profiles) have no .name property at all - only
displayName. Since PowerShell's $null -eq $null evaluates to $True, the
.name -eq .name clause falsely matched as soon as any configured
template lacked a .name property, marking almost every tenant-only
Intune policy as already templated and suppressing its deviation.

Conditional Access matching was unaffected because it only ever compares
.displayName, with no .name fallback/collision risk - matching the
reported symptom where CA drift worked but Intune drift did not.

Fix: compare the already-computed, normalized effective names
($TemplatePolicyName/$TenantPolicyName, which fall back from
displayName to name) instead of the raw properties, and require both
sides to be non-empty before treating them as a match.

Fixes KelvinTegelaar/CIPP#6347

Author: MWG-Logan

Modules/CIPPCore/Public/Get-CIPPDrift.ps1

@@ -379,10 +379,14 @@ function Get-CIPPDrift {
                 foreach ($TemplatePolicy in $TemplateIntuneTemplates) {
                     $TemplatePolicyName = if ($TemplatePolicy.displayName) { $TemplatePolicy.displayName } else { $TemplatePolicy.name }
 
-                    if ($TemplatePolicy.displayName -eq $TenantPolicy.Policy.displayName -or
-                        $TemplatePolicy.name -eq $TenantPolicy.Policy.name -or
-                        $TemplatePolicy.displayName -eq $TenantPolicy.Policy.name -or
-                        $TemplatePolicy.name -eq $TenantPolicy.Policy.displayName) {
+                    # Compare using the resolved effective names (displayName, falling back to name)
+                    # and require both sides to be non-empty. Most Intune policy types (compliance
+                    # policies, device configurations, group policy configs, etc.) only expose
+                    # displayName and have no .name property at all, so comparing raw .name values
+                    # directly (as before) compared $null -eq $null, which is $true in PowerShell -
+                    # causing every tenant policy to falsely "match" the first template as soon as
+                    # any template lacked a .name property, suppressing all tenant-only deviations.
+                    if ($TemplatePolicyName -and $TenantPolicyName -and $TemplatePolicyName -eq $TenantPolicyName) {
                         $PolicyFound = $true
                         break
                     }