Parquet: Fix column pruning for deeply nested fields

[sriharshaj]

This PR addresses a performance issue related to column pruning in nested structures when reading Iceberg tables using Parquet files.

Issue

In the current implementation of PruneColumns#struct, we are including the entire parent column in the read schema, even when only a subset of nested fields is required. This occurs because:

The originalField is being added to the filteredFields regardless of whether the passed filtered field is already present. This behavior causes the entire parent column to be read if any leaf node within the nested structure is selected in a query.

Proposed solution

I updated the code to use passed filtered field when present, and use originalField when passed filtered field is null.

[sriharshaj]

I am not sure whether the use of originalField even when field is present is intentional behavior or a bug.

[sriharshaj]

Following can be the issues related to this:
#12428
#11617