[Enhancement] Support querying Iceberg tables that have been REPLACE PARTITION FIELD

[lipenglin]

Why I'm doing:

spark-sql>
CREATE TABLE hive_prod.testdb.sample (id bigint, data string, category string)
USING iceberg PARTITIONED BY (category);
ALTER TABLE hive_prod.testdb.sample REPLACE PARTITION FIELD category with category AS category_111;
INSERT INTO hive_prod.testdb.sample VALUES (1, 'a', 'A'), (2, 'b', 'B'), (3, 'c', 'C');

spark-sql> select * from hive_prod.testdb.sample;
2       b       B
3       c       C
1       a       A
Time taken: 0.437 seconds, Fetched 3 row(s)

impala> select * from sample;
+----+------+----------+
| id | data | category |
+----+------+----------+
| 3  | c    | C        |
| 1  | a    | A        |
| 2  | b    | B        |
+----+------+----------+

sr:
MySQL [testdb]> select * from sample;
ERROR 1064 (HY000): Cannot invoke "com.starrocks.catalog.Column.getName()" because "x" is null

What I'm doing:

Iceberg tables field.name may not necessarily be partition-spec.field.name for identity Partition Transforms, field.name should be identified using partition-spec.field.source-id in schema.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.2
  • 3.1
  • 3.0
  • 2.5

[imay]

Can you comment here to explain the difference from PartitionField.name() and elaborate on when to use which?

[lipenglin]

Thanks for comments!

[Youngwb]

I think this function could put at IcebergTable, there is no need to be a static utils

[lipenglin]

done

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 5 / 5 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/connector/iceberg/IcebergMetadata.java	2	2	100.00%	[]
🔵	com/starrocks/catalog/IcebergTable.java	3	3	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[stephen-shelby]

LGTM,We may refactor this part after fully supporting the transformed partition.

[github-actions]

@Mergifyio backport branch-3.2

[mergify]

backport branch-3.2

✅ Backports have been created

• #38316 [Enhancement] Support querying Iceberg tables that have been REPLACE PARTITION FIELD (backport #37452) has been created for branch branch-3.2