[Iceberg] Fix argument order in bucket transforms

[ZacBlanco]

Description

Swap arguments to their correct positions in the bucketValues function.

Motivation and Context

Argument ordering is wrong and can cause incorrect data returned in queries on bucketed tables. This does not affect writing of the tables tables

Impact

• No impact to existing users. Queries which triggered improper behavior before should now return data correctly. The codepath for this only occurred in the IcebergPlanOptimizer. It's unlikely that any users encountered this as it seems the codepath required to hit this error is gated by a conditional which prevents us from utilizing the "valueTransform" with bucketed partitioning functions. code.

Test Plan

• Existing tests

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• 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

== NO RELEASE NOTE ==

[ZacBlanco]

@hantangwangd FYI after further analysis I don't believe it is actually possible to trigger this codepath because the error occurs only for the valueTransform function. The codepath which actually calls the valueTransform function prevents the bucket transform from being called here

So we won't be able to write a test for this. It is more like a cosmetic change.

[hantangwangd]

@ZacBlanco Thanks for the analysis. You are right that the constructed bucket ValueTransform is not called anywhere since enforced pushdown optimization is not applicable for bucket transform.