Errors when missing arguments

Description

A customer reported that after running dnsimple record list, he would have expected some help/hint, not an error:

> dnsimple records list
Error: accepts 1 arg(s), received 0

I would have expected the full help page after this error message, like on dnsimple records, so I understand what argument is expected

I think we don't need to show a full help page, but showing what type of argument is expected is better than just accepts 1 arg(s). This is more obvious when you run dnsimple records get without parameters.

> dnsimple records get
Error: accepts 2 arg(s), received 0

Expected Behavior or Outcome

• Missing arguments actually shows what arguments are missing.

Acceptance Criteria

• dnsimple records list without an argument shows that a zone name is missing
• dnsimple records get without an argument shows that a zone and a record ID are missing.

Resources/References

https://dnsimple.groovehq.com/tickets/526508

Notes

None

Start at the dnsimple records list and dnsimple records get command entry points and trace their argument validation. Check how the existing argument-count errors are produced, then run both commands without parameters; done means each reports the missing zone name, or zone and record ID, rather than only the counts.