fixed extra args in cmds

[Roaster05]

This PR fixes issue #293 and extends its coverage to other commands by ensuring that an error message is sent if any extra arguments are provided to commands that do not require them.

Current behavior:

./harbor-cli label create newLabel
FATA[0000] Error: accepts 0 arg(s), received 1: [newLabel]

./harbor-cli project list extra args
FATA[0000] Error: accepts 0 arg(s), received 2: [extra args]

The fix adds a PreRun step before the command is executed to exit if any arguments are provided.

[bupd]

The fix adds a PreRun step before the command is executed to exit if any arguments are provided.

We acutally don't need it. It adds unnecessary complexity

[Roaster05]

The fix adds a PreRun step before the command is executed to exit if any arguments are provided.

We acutally don't need it. It adds unnecessary complexity

Yes, we can also just add Args: cobra.NoArgs, in the cmd definition, but this will throw an error like Error: unknown command "newLabel" for "harbor label create". However, if we need to have our custom error message like the one mentioned in #293, I thought of adding a PreRun. We can also simply raise that error in the Run step itself based on the length of args