GH-49918: [C++][Parquet] Catch std::vector allocation errors in encoding fuzzer

[pitrou]

Rationale for this change

The Parquet encoding fuzzer can allocate a std::vector of an arbitrary size. This can produce OOMs in the fuzzer.

Issue found by OSS-Fuzz: https://issues.oss-fuzz.com/issues/506741109

What changes are included in this PR?

1. Use arrow::stl::allocator to delegate std::vector allocations to the fuzzing memory pool
2. Catch any std::vector allocation exceptions and convert them to regular Status errors

Are these changes tested?

Yes, by new regression file.

Are there any user-facing changes?

No.

• GitHub Issue: [C++][Parquet] Catch std::vector allocation errors in encoding fuzzer #49918

[pitrou]

@github-actions crossbow submit -g cpp

[github-actions]

Revision: 7c9ea2f

Submitted crossbow builds: ursacomputing/crossbow @ actions-679913723d

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-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

[wgtmac]

Why explicit is removed?

[pitrou]

Because it allows writing PoolVector<c_type> chunk_values(pool()); without having to spell out the allocator instantiation explicitly.