ORC writer API changes for granular statistics

[mythrocks]

Depends on #10041.

The erstwhile ORC writer API exposed only a binary choice to choose
the level of statistics: ENABLED/DISABLED.
This commit allows the ORC writer to further choose whether statistics
are collected at the ROW_GROUP or STRIPE level.

This commit also includes the relevant changes to java/ and python/.

[mythrocks]

This branch includes the changes from #10041, since it's based on vuule:fea-rowgroup-stats.

[vuule]

Looks good, just a few small suggestions.

Kind of scary that tests did not require any changes. I'd like to add a test with ~1M rows and various data types that runs with different stat frequency. Would be even better to reuse an existing test, will look into this.

[mythrocks]

(Please pardon the force push.)
It appears that when the statistics frequency is set to STRIPE, there we have trouble reading back the statistics, as evidenced by the failures in test_orc_writer_statistics_frequency():

/home/mithunr/anaconda3/envs/cudf-dev-11.5-3/lib/python3.8/site-packages/pyarrow/orc.py:75: in __init__
    self.reader.open(source)
pyarrow/_orc.pyx:58: in pyarrow._orc.ORCReader.open
    ???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

>   ???
E   OSError: Failed to parse the footer from ArrowInputFile

pyarrow/error.pxi:114: OSError

This surfaced when attempting to add a non-default statistics frequency to test_orc_write_statistics().
Please note that test_chunked_orc_writer_statistics_frequency[STRIPE] does succeed.

[vuule]

rerun tests

[vyasr]

rerun tests

[mythrocks]

I'm working on resolving the merge conflict in orc.hpp. Need a moment to re-run the tests locally.

[vuule]

🔥 🔥

[mythrocks]

Merging shortly.

[mythrocks]

@gpucibot merge

[mythrocks]

I've just merged this change.
@vuule: Thank you for the guidance, reviews, and help with the bugs!
@galipremsagar, @devavret, @jlowe, @cwharris: Thank you for the reviews.