[HUDI-9360] Deprecate builtin Avro payloads with mergers

[linliu-code]

Change Logs

1. Create EventTimeBasedAvroRecordMerger for event time ordering merge mode.
2. Update the place where HoodieAvroRecordMerger is called.

Impact

Remove some payloads.

Risk level (write none, low medium or high below)

Low.

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the ticket number here and follow the instruction to make changes to the website.

Contributor's checklist

• [ ] Read through contributor's guide
• [ ] Change Logs and Impact were stated clearly
• [ ] Adequate tests were added if applicable
• [ ] CI passed

[danny0405]

Hi, @linliu-code do we have a clear tutorial on how to use the new mergers, should we add a new strategy id for each merger class or just use the CUSTOM strategy id.

[linliu-code]

Hi, @linliu-code do we have a clear tutorial on how to use the new mergers, should we add a new strategy id for each merger class or just use the CUSTOM strategy id.

Let me finish adding one more test.

[hudi-bot]

CI report:

• 38f5e6afc854f71db704b5ce24ba4403184319ac UNKNOWN
• 91db80bd15f26e806ceb9201ac1a09ec3071bb1f UNKNOWN
• f3bcee1e2edbcb1d5774e0b36fef54da01d6bf50 Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

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

[vinothchandar]

@linliu-code can we close this in favor of the new approach