Don't add an autolink-extract job unless actually linking ELF/Wasm objects, matching the original C++ driver

[finagolfin]

This is needed for swiftlang/swift#69564, which enables building the early swift driver and running tests from the compiler validation suite with it for the first time on the linux CI. Looking at those test failures, I noticed that the Swift toolchain wrongly runs autolink-extract on linux when simply compiling object files, which is obviously unused:

> ./swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swiftc -c swift/test/Interpreter/hello_toplevel.swift -v Swift version 5.11-dev (LLVM e22c96610989bdb, Swift bd372c2d6861ce3) Target: x86_64-unknown-linux-gnu /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swift-frontend -frontend -c -primary-file swift/test/Interpreter/hello_toplevel.swift -target x86_64-unknown-linux-gnu -disable-objc-interop -color-diagnostics -new-driver-path /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swift-driver -empty-abi-descriptor -resource-dir /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/lib/swift -module-name hello_toplevel -plugin-path /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/lib/swift/host/plugins -plugin-path /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/local/lib/swift/host/plugins -o hello_toplevel.o /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swift-autolink-extract hello_toplevel.o -o /tmp/TemporaryDirectory.3RqPzu/hello_toplevel-1.autolink 

and which the old C++ driver doesn't:

> ./swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swiftc -c swift/test/Interpreter/hello_toplevel.swift -disallow-use-new-driver -v <unknown>:0: warning: legacy driver is now deprecated; consider avoiding specifying '-disallow-use-new-driver' Swift version 5.11-dev (LLVM e22c96610989bdb, Swift bd372c2d6861ce3) Target: x86_64-unknown-linux-gnu /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/bin/swift-frontend -frontend -c -primary-file swift/test/Interpreter/hello_toplevel.swift -target x86_64-unknown-linux-gnu -disable-objc-interop -color-diagnostics -plugin-path /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/lib/swift/host/plugins -plugin-path /home/foo/swift-DEVELOPMENT-SNAPSHOT-2023-10-30-a-ubuntu20.04/usr/local/lib/swift/host/plugins -module-name hello_toplevel -o hello_toplevel.o 

That's because the old driver checks if it shouldLink() before scheduling an autolink-extract, whereas there's no equivalent check in this repo going back to when the autolink-extract job was added in c4bf245. That's why @eeckstein had to add this linux-specific hack for these tests he added in #1019, which can now be removed and acts as a regression test.

The autolink-extract could also be disabled for static libraries, but I kept the behavior the same across both drivers instead.

[finagolfin]

@bnbarham, need a CI run here.

[artemcm]

@swift-ci test

[finagolfin]

Mac and linux CI passed; Windows CI appears to be broken right now, but doesn't matter because this pull changes nothing for Windows.

[artemcm]

@swift-ci test Windows platform

[finagolfin]

Windows CI failed again with the same error unrelated to this pull.

[finagolfin]

Looks like the Windows CI is passing again on the main compiler repo, one more Windows run here now and it should pass, @artemcm.

[artemcm]

@swift-ci test Windows platform

[finagolfin]

@compnerd, the Windows CI is repeatedly failing on this repo when installing ICU, unrelated to these driver pulls:

Copy-Item : Could not find a part of the path 'C:\Users\swift-ci\jenkins\workspace\swift-driver-PR-windows\icu\icu4c\'. At C:\Users\swift-ci\jenkins\workspace\swift-driver-PR-windows\swift\utils\build.ps1:990 char:7 + Copy-Item $SourceCache\swift-installer-scripts\shared\ICU\CMake ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Copy-Item], DirectoryNotFoundException + FullyQualifiedErrorId : System.IO.DirectoryNotFoundException,Microsoft.PowerShell.Commands.CopyItemCommand 

Does something need to be adjusted on this CI?

[compnerd]

@finagolfin could you please file an issue on apple/swift and include @shahmishal? I think that there were some tweaks that were needed as old revisions were being checked out.

[shahmishal]

@swift-ci test Windows platform