GH-48588 [C++] Migrate to stdlib span

[Anakin100100]

Rationale for this change

C++ 20 already includes a span implementation so there is no reason to maintain a custom one in utils as described in #48588

What changes are included in this PR?

arrow::utils::span definition and tests are removed and usages are replaced with std::span. Some span comparisons in tests are replaced from ASSERT_EQ to ASSERT_TRUE(std::ranges::equal(span1, span2)) because ASSERT_EQ inernally relies on == operator which is not defined for some types that we used to compare.

Are these changes tested?

Yes

Are there any user-facing changes?

No

• GitHub Issue: [C++] C++20: use std::span #48588

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview

[Anakin100100]

@pitrou can you take a look at this pr? It looks like the other one wasn't going to be finished and was stale so I made this one.

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@github-actions crossbow submit cran

[pitrou]

@Anakin100100 Can you rebase from main so that we try and get CI to pass?

[pitrou]

@github-actions crossbow submit cran

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

@github-actions crossbow submit wheelcp314*

[github-actions]

Revision: 07ffe66

Submitted crossbow builds: ursacomputing/crossbow @ actions-a82b4a5a3f

Task	Status
test-r-alpine-linux-cran
test-r-linux-as-cran
test-r-macos-as-cran

[github-actions]

Revision: 07ffe66

Submitted crossbow builds: ursacomputing/crossbow @ actions-e33421a69f

Task	Status
wheel-macos-monterey-cp314-cp314-amd64
wheel-macos-monterey-cp314-cp314-arm64
wheel-macos-monterey-cp314-cp314t-amd64
wheel-macos-monterey-cp314-cp314t-arm64
wheel-manylinux-2-28-cp314-cp314-amd64
wheel-manylinux-2-28-cp314-cp314-arm64
wheel-manylinux-2-28-cp314-cp314t-amd64
wheel-manylinux-2-28-cp314-cp314t-arm64
wheel-musllinux-1-2-cp314-cp314-amd64
wheel-musllinux-1-2-cp314-cp314-arm64
wheel-musllinux-1-2-cp314-cp314t-amd64
wheel-musllinux-1-2-cp314-cp314t-arm64
wheel-windows-cp314-cp314-amd64
wheel-windows-cp314-cp314t-amd64

[github-actions]

Revision: 07ffe66

Submitted crossbow builds: ursacomputing/crossbow @ actions-43b13ce765

Task	Status
example-cpp-minimal-build-static
example-cpp-minimal-build-static-system-dependency
example-cpp-tutorial
test-build-cpp-fuzz
test-conda-cpp
test-conda-cpp-valgrind
test-debian-13-cpp-amd64
test-debian-13-cpp-i386
test-debian-experimental-cpp-gcc-15
test-fedora-42-cpp
test-ubuntu-22.04-cpp
test-ubuntu-22.04-cpp-20
test-ubuntu-22.04-cpp-bundled
test-ubuntu-22.04-cpp-emscripten
test-ubuntu-22.04-cpp-no-threading
test-ubuntu-24.04-cpp
test-ubuntu-24.04-cpp-bundled-offline
test-ubuntu-24.04-cpp-gcc-13-bundled
test-ubuntu-24.04-cpp-gcc-14
test-ubuntu-24.04-cpp-minimal-with-formats
test-ubuntu-24.04-cpp-thread-sanitizer

[pitrou]

@WillAyd The C++ Meson failure here is probably an easy fix, do you perhaps want to push a fix on this PR or rather do it in another PR?

[pitrou]

LGTM and CI looks green except for C++ Meson (other failures are unrelated).