Fix the issue where query with DistinctLimit failed due to turning on delete as join optimization

[wypb]

Description

com.facebook.presto.iceberg.optimizer.IcebergEqualityDeleteAsJoin.DeleteAsJoinRewriter#visitTableScan returns FilterNode's outputVariables will contain the $data_sequence_number column from the table on the right side of ConnectorJoinNode, An exception occurs when the parent of the returned FilterNode is a DistinctLimitNode.

In fact, the $data_sequence_number column is only used in the FilterNode node, and its parent node is not used. This PR adds a ProjectNode on FilterNode that filters out the $data_sequence_number column.

Fixes #22105

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

Iceberg Changes
* Fix the issue where query with DistinctLimit failed due to turning on delete as join optimization.

CC: @tdcmeehan @yingsu00 @jasonf20

[jasonf20]

LGTM

[jasonf20]

nit: I think it's a little cleaner to use !IcebergMetadataColumn.isMetadataColumnId here

[wypb]

!IcebergMetadataColumn.isMetadataColumnId  doesn't work here, Because the value of variableReferenceExpression#name is similar to $data_sequence_number_7.

[jasonf20]

Ah you only have the variable references. I guess it's fine like this 👍

[tdcmeehan]

LGTM. Please reword the commit message. Perhaps

Fix equality delete with DistinctLimit

CONTEXT