branch-4.1:[fix](iceberg)fix core when read a iceberg table that have schema change and equality delete. (#59984)

[hubgeter]

bp #59984
Problem Summary:
This PR addresses three major issues related to reading Iceberg tables:

1. When reading an Iceberg table that contains equality delete files, a crash may occur if schema changes have been applied to the affected columns.
   The root cause is that the previous implementation matched columns by column name when applying equality deletes. However, Iceberg requires matching columns by Iceberg field ID to correctly identify the original column across schema evolution.
   This PR updates the equality delete logic to resolve columns using Iceberg IDs instead of column names.

2. For Iceberg tables migrated from Hive, legacy data files do not contain Iceberg field IDs.
   In this case, columns must be resolved using the table property schema.name-mapping.default.
   This PR adds support for using the name mapping defined in table properties to correctly match columns when reading such data files.

3. Reduce Thrift metadata overhead during table reads. To optimize read performance, this PR reduces the amount of Thrift metadata transmitted when reading Iceberg tables. History_schema_info now includes only the columns required for the read, including pruning of nested fields within complex types.

Handle Iceberg data files with missing field IDs.
Fix equality delete handling for Iceberg tables with schema changes.

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[hubgeter]

run buildall

[doris-robot]

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	78.54% (1786/2274)
Line Coverage	64.37% (32032/49759)
Region Coverage	65.23% (16029/24572)
Branch Coverage	55.73% (8535/15314)

[hubgeter]

run buildall

[doris-robot]

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	78.47% (1786/2276)
Line Coverage	64.27% (32030/49838)
Region Coverage	65.09% (16020/24612)
Branch Coverage	55.66% (8539/15340)

[hello-stephen]

FE UT Coverage Report

Increment line coverage 70.75% (75/106) 🎉
Increment coverage report
Complete coverage report

[morningman]

run buildall

[doris-robot]

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	78.47% (1786/2276)
Line Coverage	64.26% (32024/49838)
Region Coverage	65.11% (16024/24612)
Branch Coverage	55.61% (8530/15340)

[hello-stephen]

BE UT Coverage Report

Increment line coverage 11.09% (67/604) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	52.84% (19587/37068)
Line Coverage	36.14% (182533/505079)
Region Coverage	32.43% (140956/434593)
Branch Coverage	33.65% (61900/183951)

[hello-stephen]

BE Regression && UT Coverage Report

Increment line coverage 3.64% (22/604) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	69.47% (25200/36276)
Line Coverage	52.03% (261912/503366)
Region Coverage	49.46% (216908/438564)
Branch Coverage	50.78% (93673/184477)