Fix telemetry unsupported async

[DavidGOrtega]

yargs fail do not support await if used the app throws a strange uncontrolled ecmascript exception. Due to this unhandledexception and unhandledrejection events were triggered raising analytics three times that would not even execute doe the the ecmascript exception.

yargs seems also the throw the error after the fail function, something that it does not do it with the default handler.

This PR follow the amazing work that @0x2b3bfa0 did at #1124 to simplify the telemetry however the approach due to the mentioned error is a bit different

• closes cml on failure is sending statistics three times #1128
• closes cml on failure is printing a huge stacktrace #1127
• closes Simplify duplicate telemetry sending logic #1124

[0x2b3bfa0]

Not tested (away from keyboard) but looks good. Have you considered then() and catch() instead of that bald-eagle-nested await block?

[DavidGOrtega]

Have you considered then() and catch() instead of that bald-eagle-nested await block?

Which one?
in any case then should not even considered by any meaning

[0x2b3bfa0]

Looks good to me! 🎉