[SPARK-51943] Upgrade setup-swift to 3.0 dev version

[dongjoon-hyun]

What changes were proposed in this pull request?

This PR aims to upgrade setup-swift to next tag in order to test setup-swift 3.0 dev version.

• Setup Swift more Swiftly 🚀 (setup-swift 3.0) swift-actions/setup-swift#710

Why are the changes needed?

To fix the flakiness issues during Swift installation on linux environment.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Pass the CIs.

Was this patch authored or co-authored using generative AI tooling?

No.

[dongjoon-hyun]

Could you review this GitHub Action infra PR when you have some time, @yaooqinn ?

[yaooqinn]

can we replace this with the hash to satisfy ASF GitHub Actions Policy

External actions
You MAY use all actions internal to the apache/, github/ and actions/* namespaces without restrictions.

You MUST pin all external actions to the specific git hash (SHA1) of the action that has been reviewed for use by the project. For instance, you MUST pin foobar/baz-action@8843d7f92416211de9ebb963ff4ce28125932878.

[dongjoon-hyun]

Thank you, @viirya and @yaooqinn .

Let me try to use hash.

[dongjoon-hyun]

BTW, we don't use hash yet in Apache Spark repo, do we?

$ git grep setup-java | head -n1
.github/workflows/benchmark.yml:        uses: actions/setup-java@v4

In setup-java, v4 is just an alias for specific versions like v4.7.1

• https://github.com/actions/setup-java/tags

[yaooqinn]

Hi @dongjoon-hyun, apache/, github/ and actions/* prefixed ones can be used w/o restrictions

[yaooqinn]

+1, LGTM

[dongjoon-hyun]

Thank you! Merged to main.

I'll keep tracking the upstream and update the githash time to time until the official 3.0 comes out.