V3 preview: Inconsistent error reporting

[MichalVasak]

Describe the bug

The error output for 2 similar user errors looks very different:

MISSPELLED command parameter (new format in v3):
Unable to perform this operation due to the following problem.
Unknown argument: systemm
Command failed due to improper syntax
Command entered: "endevor list elements * --systemm ssssssssssssssssssssssssssssssss"
Available commands are "defaults, features, type-sequence, dialog, symbols, instances, code-page-config, environments, stages, systems, subsystems, types, processor-groups, processor-symbols, packages, elements, tasks".
Use "zowe endevor list --help" to view groups, commands, and options.

Response From Service
Error: Unknown argument: systemm

Diagnostic Information
Unknown argument: system

Command parameter value too long:
Syntax Error:
Invalid value length for option:
--system

You specified a string of length 32:
ssssssssssssssssssssssssssssssss

The length must be between 1 and 8 (inclusive)

Example:

• List elements in Endevor from the specified inventory location with the endevor profile set up:

  $ zowe endevor list elements -i ENDEVOR --env ENVNAME --sn 1 --sys SYSNAME --sub SUBNAME --typ TYPENAME

Use "zowe endevor list elements --help" to view command description, usage, and options.

Expected and actual results
Of course this has no impact on functionality, but at least at first glance it looks like parameter validation was overlooked when making the v3 changes to command output, so I'm reporting it just in case this is an omission.

If this is expected and intended, feel free to close the issue.

Describe your environment
CLI Version: 8.0.0-next.202407311544
Zowe Release Version: v3.0.0-prerelease
Endevor plugin custom build (testing to see if v3 broke anything)
npm v9.5.1
Windows
terminal: powershell
deamon mode disabled

Additional context

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[adam-wolfe]

Screenshot for discussion purposes:

[traeok]

Overriding error message during failure:
https://yargs.js.org/docs/#api-reference-failfn-boolean

We can use this function to print our own error instead of using the one thrown by yargs.

[adam-wolfe]

In the interest of avoiding introducing last-minute breaking changes to the V3 pre-release, we have decided to keep error messages as-is until V4.