[AMORO-4044] Fix partition mapping bug in TableEntriesScan for tables with evolved PartitionSpec

[j1wonpark]

Why are the changes needed?

The entries metadata table returns a unified super-struct partition containing fields from all PartitionSpecs. In TableEntriesScan, both buildDataFile() and buildDeleteFile() passed this unified partition directly to withPartition(), which causes a partition struct mismatch for files written under a non-latest PartitionSpec. This is the root cause of #4044.

This PR fixes the issue at the TableEntriesScan level by projecting the unified partition to the spec-specific partition type using StructProjection.createAllowMissing(), so that all callers of TableEntriesScan get correct partition values regardless of spec evolution.

Close #4044.

Brief change log

• Add projectPartition() method that uses StructProjection.createAllowMissing() to project the unified partition struct to the file's spec-specific partition type
• Apply the projection in both buildDataFile() and buildDeleteFile()
• Cache the unified partition type via Partitioning.partitionType(table) for reuse

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible
• Add screenshots for manual tests if appropriate
• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
  no
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
  not applicable