GH-41390: [CI] Use setup-python GitHub action on csharp macOS job

[raulcd]

Rationale for this change

The new macos-latest GH runner has changed and jobs are currently failing.

What changes are included in this PR?

Install python with setup-python.

Are these changes tested?

Will be on CI

Are there any user-facing changes?

No

• GitHub Issue: [CI] macOS 11 C# job fails to install python dependencies #41390

[github-actions]

⚠️ GitHub issue #41390 has been automatically assigned in GitHub to PR creator.

[raulcd]

@CurtHagenlocher there seems to be an error with .net 8 on that job now that I fixed Python:

Passed!  - Failed:     0, Passed:    25, Skipped:     0, Total:    25, Duration: 279 ms - Apache.Arrow.Compression.Tests.dll (net8.0)
The active test run was aborted. Reason: Test host process crashed : Stack overflow.
   at Python.Runtime.Runtime.PyImport_ImportModule(System.String)
   at Python.Runtime.PyModule.Import(System.String)
   at Python.Runtime.Py.Import(System.String)
   at Apache.Arrow.Tests.CDataSchemaPythonTest.ImportRecordBatchFromBuffer()
   at System.RuntimeMethodHandle.InvokeMethod(System.Object, Void**, System.Signature, Boolean)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(System.Object, System.Reflection.BindingFlags)
   at Xunit.Sdk.TestInvoker`1[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].CallTestMethod(System.Object)
   at Xunit.Sdk.TestInvoker`1+<>c__DisplayClass46_0+<<InvokeTestMethodAsync>b__1>d[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Xunit.Sdk.TestInvoker`1+<>c__DisplayClass46_0+<<InvokeTestMethodAsync>b__1>d[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], xunit.execution.dotnet, Version=2.7.1.0, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c]](<<InvokeTestMethodAsync>b__1>d<System.__Canon> ByRef)
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Xunit.Sdk.TestInvoker`1+<>c__DisplayClass46_0+<<InvokeTestMethodAsync>b__1>d[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], xunit.execution.dotnet, Version=2.7.1.0, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c]](<<InvokeTestMethodAsync>b__1>d<System.__Canon> ByRef)
   at Xunit.Sdk.TestInvoker`1+<>c__DisplayClass46_0[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].<InvokeTestMethodAsync>b__1()
   at Xunit.Sdk.ExecutionTimer+<AggregateAsync>d__4.MoveNext()
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Xunit.Sdk.ExecutionTimer+<AggregateAsync>d__4, xunit.execution.dotnet, Version=2.7.1.0, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c]](<AggregateAsync>d__4 ByRef)
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[Xunit.Sdk.ExecutionTimer+<AggregateAsync>d__4, xunit.execution.dotnet, Version=2.7.1.0, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c]](<AggregateAsync>d__4 ByRef)
   at Xunit.Sdk.ExecutionTimer.AggregateAsync(System.Func`1<System.Threading.Tasks.Task>)
   at Xunit.Sdk.TestInvoker`1+<>c__DisplayClass46_0[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].<InvokeTestMethodAsync>b__0()
   at Xunit.Sdk.ExceptionAggregator+<RunAsync>d__9.MoveNext()

I am unsure on what the issue is.

[CurtHagenlocher]

Thanks @raulcd. I'll take a look.

[CurtHagenlocher]

I can confirm that this repros locally on my M1 Mac.

[raulcd]

Thanks @CurtHagenlocher , I am happy to both merge this and fix the issue on a different PR or you can pick this change and provide the .NET fix on a separate one :)

[CurtHagenlocher]

I filed #41397 for the test failure. I can repro it even with an older maintenance branch using .NET 7.0 so there seems to be something more going on than just the .NET upgrade. I think this PR should be committed while I try to figure things out.

[raulcd]

👍 merging as discussed on the PR.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 15986ae.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 16 possible false positives for unstable benchmarks that are known to sometimes produce them.