[HUDI-8097] Fix getting Schema evolution setting from hudi-defaults.conf on altering columns

[wombatu-kun]

Change Logs

Value of hoodie.schema.on.read.enable from externalized config hudi-defaults.conf was not taken into consideration while processing commands such as alter table change column .. in Spark.
Fixed it by utilzing DFSPropertiesConfiguration.getGlobalProps in HoodieCatalog.loadTable and SparkXXResolveHudiAlterTableCommand.apply.
Removed code duplicates in SparkXXResolveHudiAlterTableCommand classes by moving common method isSchemaEvolutionEnabled to ProvidesHoodieConfig.

Impact

Schema evolution option from hudi-defaults.conf works properly now with Spark SQL alter table change colunm.

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

none

Documentation Update

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:

• 35cf6b2 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[danny0405]

+1, I like the fix.