fix: Fallback to field.name to get field position when PARQUET:field_id is unavailable

[CTTY]

Which issue does this PR close?

• Closes Need to use field.name to determine arrow field's position when PARQUET:field_id is unavailable #1560

What changes are included in this PR?

• Fallback to use field.name to get field position
• Minor typo fixes

Are these changes tested?

Yes, added uts

[liurenjie1024]

Let's discuss in this issue: #1560 (comment)

[liurenjie1024]

I think we still have misunderstanding here. As I have said #1560 (comment) , for the nan_val_cnt case, we should match field to arrow array using the field's position(e.g. the rank of this field in struct) rather than by id or name. It's not easy to accomplish with currentl interface, so we should change the interface of PartnerAccessor, see comments below.

[Fokko]

@CTTY Thanks for raising this PR, as suggested in #1560 I think we need to rely on name-mapping here.

Iceberg is designed to do operations lazy, meaning that we typically don't rewrite data unless it is neccessary. For example, if you rename a field, it will still find the field with the original name using the field-IDs. This is the case when you have a new table that has the field-IDs correctly set.

However, in the age of big-data, and to make it easier for users to migrate to Iceberg, we also support importing existing Parquet files where the field-IDs are missing. In this case, we'll use name-mapping to map names to a field-ID. In the case of a rename, the old and the new name will map to the same ID, so we can still look up the field after a rename.