WIP: [Parquet] Add tests for IO/CPU access in parquet reader

[alamb]

Which issue does this PR close?

• This is part of the work to add cache to the Parquet Reader in Parquet filter pushdown v4 #7850

Rationale for this change

There is quite a bit of cleverness in parquet reader related to IO patterns. To ensure we don't introduce regressions in the existing code, I would like to add tests that cover the IO patterns of the Parquet Reader.

I eventually would like to revisit the "minimize IO at all costs" design of the parquet reader (for use cases where the file is local, for example) but to do that I think we need to better understand what the current reader does

What changes are included in this PR?

Add a new test:

1. Creates a temporary parquet file with a known row group structure
2. Reads data from that file using the Arrow Parquet Reader, recording the IO operations
3. Asserts the expected IO patterns based on the read operations

This is done for both the sync and async readers.

Are these changes tested?

This is only tests

Are there any user-facing changes?

[alamb]

Update here is I am quite pleased with how the sync reader looks. Now I am working on sorting out how to test the async reader