GH-36682: [C++] Add missing ARROW_ACERO dependency to ARROW_PYTHON

[kou]

Rationale for this change

PyArrow wants Acero.

What changes are included in this PR?

Add ARROW_ACERO to ARROW_PYTHON dependency.

Are these changes tested?

Yes.

Are there any user-facing changes?

Yes.

• Closes: [C++] ARROW_PYTHON misses ARROW_ACERO dependency #36682

[kou]

@github-actions crossbow submit example-python-minimal-*

[github-actions]

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

[kou]

@github-actions crossbow submit example-python-minimal-*

[kou]

I've opened #36683 for the example-minimal-python-* failures.

[raulcd]

I am not entirely sure I understand why are we doing this change. Should all ARROW_PYTHON dependencies be added? what about S3 or GCS?

[jorisvandenbossche]

Also, shouldn't we in theory not rely on this in our own CI, given that it is a deprecated option?

If the minimal python build needs this, then we should just enable ARROW_ACERO directly in that build? (or update it to not require acero)

[kou]

Sorry. This is needless.
I thought that this is the cause of #36680 but it was wrong: #36683

I thought that this is still needed because #34711 removes ARROW_COMPUTE from ARROW_PYTHON instead of replacing ARROW_COMPUTE with ARROW_ACERO.
But it's correct because ARROW_PYTHON depends on ARROW_ACERO implicitly: ARROW_PYTHON -> ARROW_DATASET -> ARROW_ACERO

[kou]

I withdraw this because this is needless.

[github-actions]

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