test: Add coverage for with OverwriteWithLatestAvroPayload with ordering fields set

[rahil-c]

Describe the issue this Pull Request addresses

• This is a follow up pr from test: add functional payload test cases for v6 (OverwriteWithLatestAvroPayload, DefaultHoodieRecordPayload) #14041, which seeks to add test coverage for a special case where a user created a MOR v6 table with an older 0.x writer, and with an ordering field explicitly set. In order to achieve this we needed to add a test in the payload fixtures approach, as the other pr had a limitation of using a 1.1.x writer when creating a v6 table (which has some inconsistency in the behavior around OverwriteWithLatestAvroPayload now not handling ordering values in 1.1.0)

Summary and Changelog

• Modified the scala payload script, to simplify the batches of data preupgrade (only having higher ordering values)
• Added specific mixed ordering values post upgrade for this case, as well as validation that data is following event time semantics.

Impact

None

Risk Level

None

Documentation Update

None

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable

[rahil-c]

need to add back default payload

[hudi-bot]

CI report:

• 31eccf6 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build