[SUPPORT] Ensure `hoodie.datasource.write.keygenerator.type` internally sets `hoodie.datasource.write.keygenerator.class` and respects the table config validation across all code flows

[bhasudha]

Tips before filing an issue

• Have you gone through our FAQs?

• Join the mailing list to engage in conversations and get faster support at dev-subscribe@hudi.apache.org.

• If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced We have hoodie.datasource.write.keygenerator.type that can internally instantiate hoodie.datasource.write.keygenerator.class. However the table config validations check only for hoodie.datasource.write.keygenerator.class. This creates ambiguity as to which property will take precedence and what will be honored.

To Reproduce

Steps to reproduce the behavior:

Expected behavior

A clear and concise description of what you expected to happen.

Environment Description

• Hudi version :

• Spark version :

• Hive version :

• Hadoop version :

• Storage (HDFS/S3/GCS..) :

• Running on Docker? (yes/no) :

Additional context

Add any other context about the problem here.

Stacktrace

Add the stacktrace of the error.

[xushiyan]

For @lokeshj1703 to look further and present some ideas for discussion. The plan here should be: 1) understand the usage difference btw these 2 similar configs throughout the codebase. 2) think of an approach to make 1 config taking precedence and the other as fallback and deprecated. 3) Once the approach can be confirmed, then can come up with a fix and introduce the changing usage in release notes.