refactor: refactoring Narg checks

[ameeetgaikwad]

Related Issues

#12790

Proposed Changes

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title conforms with contribution conventions
• Update CHANGELOG.md or signal that this change does not need it per contribution conventions
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rvagg]

@ameeetgaikwad I think we need to be a bit more complete with this, have a look for instances of ctx.Args (specifically cctx.Args() usually but ctx.Args is a good shortening that should catch variations), and then walk back in the commands to see if there is a check there. Doing this in cli and doing a quick browse of the initial results I can see slash-consensus seems to need a check for 2 but doesn't have one. evm.go has its own custom error method (if argc := cctx.Args().Len(); argc != 1 {) which we probably should make consistent and use the IncorrectNumArgs function (I'm not sure there's a good reason to do it this way, seems like copypasta code to me). I've only looked through the first few files and haven't even touched miner or worker. It would be good here to be a bit more exhaustive than just fixing the obvious ones.