GH-46871: [C++][Parquet] Restore implementation of 3 arrow::FileReader::GetRecordBatchReader() functions

[rouault]

Rationale for this change

Those functions were accidentally removed in f7bc271 whereas only the variants using unique_ptr<> were intended for removal.

What changes are included in this PR?

Restore the implementation of 3 functions whose prototype is still available

Are these changes tested?

Apparently no

Are there any user-facing changes?

No (unbreak a unreleased regression)

Cf #46867 (comment) for discussion

• GitHub Issue: [C++][Parquet] Restore implementation of 3 arrow::FileReader::GetRecordBatchReader() functions #46871

[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

[kou]

Could you open a new issue for this?

[AlenkaF]

Thank you for catching this and making a PR @rouault, much appreciated!
I have opened an issue here: #46871

[github-actions]

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

[github-actions]

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

[conbench-apache-arrow]

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

There were 119 benchmark results with an error:

• Commit Run on arm64-t4g-2xlarge-linux at 2025-06-23 10:55:15Z
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-07, scale_factor=1
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-09, scale_factor=1
• and 117 more (see the report linked below)

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.