Send analytics on a best-effort basis

Long ago @hbagdi added #254. This seems to no longer be the case.

Understand why this was changed, and if appropriate make analytics a best-effort request and ensure that they do not impact end user functionality by adding latency to the command.

Start by reviewing the change referenced in #254 and tracing where analytics requests run during the command. Determine whether the request can add latency or affect command success; done means analytics operate on a best-effort basis without impacting end-user functionality.

Written by the indexing model from the issue text.