)

deleting the repo level coc in favor of the org wide coc in the .github repo. this file present means that it opts-out of that.

removing redundant info

This is mismatching the other init which is public.

#479)

The build is generating warnings about extra space after
`@availability` and before the `(`.

rdar://133952407

This aligns the implementation of resolveSymlinks with that of Foundation.String._resolvingSymlinksInPath, which received this canonicalization fix in swiftlang/swift-foundation#639.

#486)

Analogous fix to swiftlang/swift-package-manager#8047

We only build and test swift-tools-support-core with this multiroot-data-file, so there’s no reason why it should include any other projects.

Currently, `FILEPointer` is typealiased to `OpaquePointer` for Musl:

```swift
#if os(Android) || canImport(Musl)
public typealias FILEPointer = OpaquePointer
#else
public typealias FILEPointer = UnsafeMutablePointer<FILE>
#endif
```

But building an executable that links against TSCBasic fails:

```
$ ~/Library/Developer/Toolchains/swift-6.0.1-RELEASE.xctoolchain/usr/bin/swift build --swift-sdk x86_64-swift-linux-musl

.build/checkouts/swift-tools-support-core/Sources/TSCBasic/Process/Process.swift:706:70: error: cannot convert value of type 'UnsafeMutablePointer<FILE>' (aka 'UnsafeMutablePointer<_IO_FILE>') to expected argument type 'FILEPointer' (aka 'OpaquePointer')
 704 |             throw Process.Error.stdinUnavailable
 705 |         }
 706 |         let stdinStream = try LocalFileOutputByteStream(filePointer: fp, closeOnDeinit: true)
     |                                                                      `- error: cannot convert value of type 'UnsafeMutablePointer<FILE>' (aka 'UnsafeMutablePointer<_IO_FILE>') to expected argument type 'FILEPointer' (aka 'OpaquePointer')
```

But removing the `canImport(Musl)` check allows it to compile without issue, so I assume it was put there for an earlier version of the Musl SDK (or that it was never tested).

…another process (#490)