POM should not redefine Maven Central

You latest POM (found [here|https://repo.maven.apache.org/maven2/org/apache/hudi/hudi/0.14.0/hudi-0.14.0.pom]) have several issues:
* redefines "central" as "Maven Central". There is no need to define Maven Central as it comes "out of the box" with Maven
* adds Cloudera repository group *public* to the build, that is a big no-no, as group seems to contain Maven Central proxy. For example, it has [junit:junit:4.12|https://repository.cloudera.com/repository/public/junit/junit/4.12/junit-4.12.pom] (in fact am unsure WHAT you need from here, as I did not found any *hosted* repository that has any content, or is not public. Maybe they need to enable anon access to some of their hosted repository, as publishing a group ONLY that has Central is a big no-no).
* adds repository Confluent without any restriction

These should be fixed.

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-7339
- Type: Task

Start with the published hudi-0.14.0.pom linked in the issue and trace the build or release configuration that generates its repository declarations. Done means the generated POM no longer redefines Maven Central or adds unrestricted Cloudera and Confluent repositories; validate the result with Maven dependency resolution.

Written by the indexing model from the issue text.