[EPIC] Refactor the validation logic in the commands.

[Abyss-lord]

What would you like to be improved?

Refactor the client Command parameter validation logic. Let the command do its own validation, and GravitinoCommandLine only handle the common part of the logic validation

How should we improve?

Refactor the client Command parameter validation logic by introducing a verify method in the Command class for parameter validation. the verify method as follows:

 public Command verify() {
    // validation logic
    return this;
  }

In GravitinoCommandLine, Use newXXX().verify.handle() to invoke specific commands

Task list

• [Subtask] Refactor the validation logic of Metalake #6086
• [Subtask] Refactor the validation logic of Catalog #6087
• [Subtask] Refactor the validation logic of Schema and Table #6105
• [Subtask] Refactor the validation logic of user and group #6106
• [Subtask] Refactor the validation logic of column and model #6112
• [Subtask] Refactor the validation logic of topic and fileset #6121
• [Subtask] Refactor the validation logic of tag and role #6123

[Abyss-lord]

@justinmclean I would like to work on it.

[Abyss-lord]

@justinmclean , The scope of a single task is too broad. Should we consider splitting it into smaller tasks for better manageability? just like

• refactor metalake command and test case.

[justinmclean]

I don't think it is too large, but if you want to break it by entity (metalake, catalog, schema etc ect) go ahead.