Use new way when building paths based on triple.

In TSC pr #229 and SPM pr #3576, we introduced a method named
`platformBuildPathComponent` to distinguish the valid platform path name
versus the valid target name, where one may have an embedded version
number and the other may not.

SourceKit test suite SwiftPMIntegrationTests currently fails. This is
presumably because this change may be required as it is one of two
uses of `tripleString`. The other uses `tripleString` as the value for
the `-target` field, so it is correct as written. The other -- as in
this commit -- builds a path.

This commit must be committed in concert with the aforementioned prs.

Author: 3405691582

Sources/SKSwiftPMWorkspace/SwiftPMWorkspace.swift

@@ -117,7 +117,7 @@ public final class SwiftPMWorkspace {
     }
 
     self.buildParameters = BuildParameters(
-        dataPath: location.workingDirectory.appending(component: triple.tripleString),
+        dataPath: location.workingDirectory.appending(component: triple.platformBuildPathComponent()),
         configuration: buildConfiguration,
         toolchain: toolchain,
         flags: buildSetup.flags

Tests/SKSwiftPMWorkspaceTests/SwiftPMWorkspaceTests.swift

@@ -605,5 +605,5 @@ private func buildPath(
   triple: Triple) -> AbsolutePath
 {
   let buildPath = config.path ?? root.appending(component: ".build")
-  return buildPath.appending(components: triple.tripleString, "\(config.configuration)")
+  return buildPath.appending(components: triple.platformBuildPathComponent(), "\(config.configuration)")
 }