[WASM] Always install CoreFoundation headers in target dir

This avoids to conflict between static and shared module.map of
CoreFoundation. The shared version of Foundation module.map doesn't
require linking CoreFoundation, but build-foundation overwrite the
shared version with static version.

Author: kateinoigakukun

utils/webassembly/build-foundation.sh

@@ -24,17 +24,9 @@ cmake -G Ninja \
 ninja -v
 ninja -v install
 
-# On macOS the target CoreFoundation shadows the CoreFoundation suppplied by Xcode.
-# On Linux though there's no system CoreFoundation, its headers have to be shipped
-# in the installable archive and serve for both host and target.
-if [[ "$(uname)" == "Darwin" ]]; then
-  mv $DESTINATION_TOOLCHAIN/usr/lib/swift_static/CoreFoundation \
-    $DESTINATION_TOOLCHAIN/usr/lib/swift/wasi/wasm32/CoreFoundation
-else
-  mv $DESTINATION_TOOLCHAIN/usr/lib/swift_static/CoreFoundation \
-    $DESTINATION_TOOLCHAIN/usr/lib/swift/CoreFoundation
-fi
+mv $DESTINATION_TOOLCHAIN/usr/lib/swift_static/CoreFoundation \
+  $DESTINATION_TOOLCHAIN/usr/lib/swift/wasi/wasm32/CoreFoundation
 
 # .swiftdoc and .swiftmodule files should live in `swift`, not in `swift_static`
 mv $DESTINATION_TOOLCHAIN/usr/lib/swift_static/wasi/wasm32/Foundation.swift* \
-  $DESTINATION_TOOLCHAIN/usr/lib/swift/wasi/wasm32
+  $DESTINATION_TOOLCHAIN/usr/lib/swift/wasi/wasm32