[Test] Disable stdlib/StaticBigInt on macOS

[xymus]

No description provided.

[tbkka]

@xymus Is there a link to the test failure? Unlike #62594, this isn't obviously a test mis-configuration issue.

CC: @benrimmington @stephentyrone

[xymus]

I updated rdar://103369837 with links to failures under macosx-x86_64 and iphoneos-arm64. The disabling in this PR didn't take effect because I forgot the x in macosx.

@tbkka Do we have a fix in sight? Otherwise we may want to disable this test on 3 platforms.

[tbkka]

The test failures we're seeing internally are all manifesting similar errors:

stderr>>> dyld: lazy symbol binding failed: Symbol not found: _$ss12StaticBigIntV22_builtinIntegerLiteralABBI_tcfC
stderr>>>   Referenced from: .../test-iphoneos-arm64/stdlib/Output/StaticBigInt.swift.tmp/a.out
stderr>>>   Expected in: /usr/lib/swift/libswiftCore.dylib

It looks like the tests need to be updated to only run when testing against a suitably new libswiftCore.dylib.

(Context: We run Swift test suites internally with the system-installed libswiftCore.dylib and with the just-built libswiftCore.dylib in order to detect issues that will affect binaries running on different OS versions. Features that don't support backwards deployment need to have their tests suitably guarded.)

[benrimmington]

@tbkka For the macOS failure, would one (or both) of the following be needed?

// UNSUPPORTED: back_deployment_runtime
// UNSUPPORTED: use_os_stdlib

Or is there some other way to guard the tests?

[tbkka]

UNSUPPORTED: use_os_stdlib is what we need for that macOS failure