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

**_Tips before filing an issue_**

- Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?

- 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](https://issues.apache.org/jira/projects/HUDI/issues) 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:

1.
2.
3.
4.

**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.```