Keep the renamed functional test socket within the macOS path bound

Use the descriptive socket filename inside the existing unique test-owned output directory. The actual checkout path is 102 characters rather than 108, within the macOS 104-character Unix socket limit. Keep every original entry-type and target-content assertion and joined cleanup.

Validation: original real Unix socket test passed (1/1, zero skips), full strict Debug solution build passed with zero warnings/errors, format verification and governance passed. The complete local and Linux qualification is being repeated on this source checkpoint.

Author: KSemenenko

tests/KeyLoad.FunctionalTests/StorageRecovery/Cases/OfflineRegular/OfflineRegularFileEntryTypeTests.cs

@@ -17,7 +17,7 @@ await WithDirectoryAsync(async root =>
             var target = Path.Combine(root, "target.bin");
             var link = Path.Combine(root, "target.link");
             var directory = Path.Combine(root, "directory");
-            var socketPath = Path.Combine(root, "local.socket");
+            var socketPath = Path.Combine(root, "socket");
             byte[] targetBytes = [0x10, 0x00, 0x90];
             await File.WriteAllBytesAsync(target, targetBytes);
             File.CreateSymbolicLink(link, target);
@@ -48,6 +48,9 @@ private static async Task WithDirectoryAsync(Func<string, Task> action)
         {
             await action(root);
         }
-        finally { Directory.Delete(root, recursive: true); }
+        finally
+        {
+            Directory.Delete(root, recursive: true);
+        }
     }
 }