[HUDI-7946][RFC 79] Add support for cancellable clustering table service plans

[kbuci]

Change Logs

Claim RFC-79 for proposal to add "cancellable" clustering table service plans, where users can configure a clustering plan to be cancelled and aborted, either on-demand or when it has write conflict with other ongoing write. As detailed in RFC, primary motivation for this functionality is if user has low-priority clustering writes that should not interfere with or delay other higher-priority operations, such as ingestion writes.

Impact

• Adding new folder to /.hoodie folder and new instant state type, though only used when a clustering plan is configured as cancellable
• All type of writes/table services (including non-cancellable clustering - the way it's done currently) should behave same as before.

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

high

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

[hudi-bot]

CI report:

• 109ea21 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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