TSCBasic: avoid validating the relative path on Windows

The generated relative path is un-anchored and thus cannot be validated
or canonicalized.  Introduce a constructor for the unsafe constructor of
a relative path and use that to create the relative path.  This enables
the construction of a non-canonical relative path for cousins.

Author: compnerd

Sources/TSCBasic/Path.swift

@@ -247,6 +247,10 @@ public struct RelativePath: Hashable {
         _impl = impl
     }
 
+    internal init(string: String) {
+        self.init(PathImpl(string: string))
+    }
+
     /// Initializes the RelativePath from `str`, which must be a relative path
     /// (which means that it must not begin with a path separator or a tilde).
     /// An empty input path is allowed, but will be normalized to a single `.`
@@ -915,7 +919,7 @@ extension AbsolutePath {
             // might be an empty path (when self and the base are equal).
             let relComps = pathComps.dropFirst(baseComps.count)
 #if os(Windows)
-            result = RelativePath(relComps.joined(separator: "\\"))
+            result = RelativePath(string: relComps.joined(separator: "\\"))
 #else
             result = RelativePath(relComps.joined(separator: "/"))
 #endif
@@ -934,11 +938,12 @@ extension AbsolutePath {
             var relComps = Array(repeating: "..", count: newBaseComps.count)
             relComps.append(contentsOf: newPathComps)
 #if os(Windows)
-            result = RelativePath(relComps.joined(separator: "\\"))
+            result = RelativePath(string: relComps.joined(separator: "\\"))
 #else
             result = RelativePath(relComps.joined(separator: "/"))
 #endif
         }
+
         assert(AbsolutePath(base, result) == self)
         return result
     }