GH-43570: [CI][Dev][Docs] Update references to "docker-compose" with "docker compose"

[amoeba]

Rationale for this change

This is a follow-on to #43566 which was merged earlier today. See #43570 for more detail on the entire set of changes.

What changes are included in this PR?

• Replace instances where we call or document calling docker-compose with docker compose.

Are these changes tested?

Yes.

Are there any user-facing changes?

This PR includes the require user-facing changes to document things.

• GitHub Issue: [CI][Dev][Docs] Consider updating all references to "docker-compose" with "docker compose" #43570

[github-actions]

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

[pitrou]

Note that more Archery changes were done in PR #43586.

[pitrou]

@amoeba Do you want to revive this PR?

[amoeba]

Yeah. Let me see what's needed to close this out now.

[amoeba]

I rebased and went through the repo again to find any instances that needed attention. Waiting for CI but I think this is ready for a review.

[amoeba]

Pushed one commit to fix the archery tests.

[amoeba]

The three CI failures don't look related to me.

[kou]

+1

[amoeba]

@kou 's suggestion encouraged me to do a more serious pass, trying to use "Docker Compose" everywhere I saw we were referring to the product/software rather than a shell command. See 71a365a. Some calls were subjective, though I think the most important thing has been done here (change docker-compose to docker compose for all example shell commands).

@pitrou do you want to take a last look here?

[pitrou]

LGTM, but I'd wait for @kou 's approval

[kou]

+1

[conbench-apache-arrow]

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

There were no benchmark performance regressions. 🎉

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

[amoeba]

Thanks for the reminder @pitrou and for the reviews, both you and @kou.