Use normalized relative paths during conflict checking

This is to prevent false negatives from mismatched path formats.

Author: Exanite

sources/SilkTouch/SilkTouch/Mods/PrettifyNames.cs

@@ -200,7 +200,7 @@ await proj.GetCompilationAsync(ct)
         var typeNamesLongestFirst = typeNames.OrderByDescending(x => x.Key.Length).ToArray();
 
         var documentPaths = proj
-            .Documents.Select(d => d.FilePath)
+            .Documents.Select(d => d.RelativePath())
             .Where(d => d != null)
             .ToHashSet();
 
@@ -223,12 +223,13 @@ await proj.GetCompilationAsync(ct)
 
             // Rename doc and update path
             var originalName = doc.Name;
-            var originalPath = doc.FilePath;
+            var originalPath = doc.RelativePath();
             doc = doc.ReplaceNameAndPath(oldName, newName);
+            var newPath = doc.RelativePath();
 
             // Check for path conflict
             documentPaths.Remove(originalPath);
-            if (!documentPaths.Add(doc.FilePath!))
+            if (!documentPaths.Add(newPath))
             {
                 logger.LogError(
                     $"{originalName} -> {doc.Name} failed to rename file as a file already exists at {doc.FilePath}"