[HUDI-8930] Set transaction manager lock requirement based on config

[codope]

Change Logs

• After removing defaut lock provider in 63ad659, we need to still set a lock for instant time geenration. See changes in HoodieWriteConfig.
• Lock requirement for transaction manager can change from within a transaction. For example, when a compaction is scheduled during upgrade, the lock requirement is set to false. Make isLockRequired non-final and provide a setter.
• TransacationManager's isLockRequired is set in BaseHoodieClient#updateColumnsToIndexWithColStats which is called before beginTransaction and then lock requirements are reset after the job within transaction is done.

Impact

Set transaction manager lock requirement based on config

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

medium

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:

• bb7e32b Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[codope]

Closing in favor of #12737