Fix CxAssistDisplayCoordinator documentation and scanner filtering

- Fix ClearFindingsFromDisabledScanners filter: use IsScannerEnabled() instead of v.Scanner != 0 check
- Remove "for testing" from UpdateFindingsForFile comment (production API)
- Align filter logic with method documentation and behavior

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: cx-rahul-pidde

ast-visual-studio-extension/CxExtension/CxAssist/Core/CxAssistDisplayCoordinator.cs

@@ -359,7 +359,7 @@ public static void RefreshProblemWindow(
         }
 
         /// <summary>
-        /// Updates findings for a specific file without a buffer (for testing or file-based updates).
+        /// Updates findings for a specific file without a buffer.
         /// Updates internal storage and raises IssuesUpdated event.
         /// </summary>
         public static void UpdateFindingsForFile(string filePath, List<Vulnerability> vulnerabilities)
@@ -414,7 +414,7 @@ public static void ClearFindingsFromDisabledScanners()
                 foreach (var filePath in _fileToIssues.Keys.ToList())
                 {
                     _fileToIssues[filePath] = _fileToIssues[filePath]
-                        .Where(v => v != null && v.Scanner != 0)
+                        .Where(v => v != null && CxAssistConstants.IsScannerEnabled(v.Scanner))
                         .ToList();
 
                     if (_fileToIssues[filePath].Count == 0)