Fix additional Windows CI issue: Escape file paths in JSON replacement

- Fixed CliWorkflow_WithConfigFileOutputSettings_ShouldUseConfigurationValues test
- Added proper JSON escaping when replacing paths in config file content
- Use .Replace('\', '\\') to escape backslashes for Windows paths
- Resolves JSON parsing error: 'U' is an invalid escapable character

This complements the previous Windows CI fix and ensures all integration
tests work correctly on Windows by properly escaping file paths when
they are inserted into JSON configuration files.

Author: jbrinkman

tests/DotNetApiDiff.Tests/Integration/CliWorkflowTests.cs

@@ -185,7 +185,9 @@ public void CliWorkflow_WithConfigFileOutputSettings_ShouldUseConfigurationValue
 
         // Update the config file to use our temp output path
         var configContent = File.ReadAllText(configFile);
-        var configWithTempPath = configContent.Replace("comparison-report.html", expectedOutputFile);
+        // Escape backslashes for JSON format on Windows
+        var escapedOutputPath = expectedOutputFile.Replace("\\", "\\\\");
+        var configWithTempPath = configContent.Replace("comparison-report.html", escapedOutputPath);
         var tempConfigFile = Path.Combine(_tempOutputPath, "temp-config.json");
         File.WriteAllText(tempConfigFile, configWithTempPath);