Unhelpful documentation when misspelling CLI commands

[Jegp]

From @aMarcireau:

My only (minor) concern with the current approach is in cases where the user writes something along the lines of:
faery input ... filter ... filter render ... outputs --file video.mp4 (notice the typo "outputs" instead of "output").

Should this happen, the user would get an error along the lines of "render has no 'outputs' parameter" or possibly "render has no '--file' flag" (if render happens to take a positional argument and 'outputs' is assumed to be that argument). This could cause frustration since the error message points in the wrong direction. Whilst this is not ideal, this may not be a major issue in practice and I do not think that this can be addressed without introducing special characters.

Two ways we could consider mitigating this is to (1) match against closely related groups ("did you mean outputs?") and (2) allow regexes in the group names.