GH-46333: [CI] Always pass --yes to mamba clean

[pitrou]

Rationale for this change

Some CI builds can get stuck before mamba clean is asking for confirmation. See example here:
https://github.com/apache/arrow/actions/runs/14855669693/job/41708331720?pr=46332

This might depend on the Mamba version and whether it implements TTY detection reliably.

What changes are included in this PR?

Always pass --yes to mamba clean.

Are these changes tested?

Yes, by definition.

Are there any user-facing changes?

No.

• GitHub Issue: [CI] Integration failing due to new mamba prompt #46333

[pitrou]

@github-actions crossbow submit test-conda-*

[github-actions]

Revision: d416610

Submitted crossbow builds: ursacomputing/crossbow @ actions-d765f8e54e

Task	Status
test-conda-cpp
test-conda-cpp-meson
test-conda-cpp-valgrind
test-conda-python-3.10
test-conda-python-3.10-hdfs-2.9.2
test-conda-python-3.10-hdfs-3.2.1
test-conda-python-3.10-pandas-latest-numpy-latest
test-conda-python-3.11
test-conda-python-3.11-dask-latest
test-conda-python-3.11-dask-upstream_devel
test-conda-python-3.11-hypothesis
test-conda-python-3.11-pandas-latest-numpy-1.26
test-conda-python-3.11-pandas-latest-numpy-latest
test-conda-python-3.11-pandas-nightly-numpy-nightly
test-conda-python-3.11-pandas-upstream_devel-numpy-nightly
test-conda-python-3.11-spark-master
test-conda-python-3.12
test-conda-python-3.12-cpython-debug
test-conda-python-3.13
test-conda-python-3.9
test-conda-python-3.9-pandas-1.1.3-numpy-1.19.5
test-conda-python-emscripten

[pitrou]

For some reason, PR #46334 only fixed the integration build. @kou @lidavidm

[lidavidm]

Ah, sorry, I only looked at integration since originally I only noticed it when it was failing PRs on arrow-java; I didn't check the other dockerfiles

[pitrou]

Wow, lots of unrelated failures here.

[conbench-apache-arrow]

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

There were no benchmark performance regressions. 🎉

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