capture only user-specified arkouda commands on client

[hokiegeek2]

Feature Description
The recently added command logging logs incoming commands along with any corresponds command arguments and requesting user. Client-side debug logging has demonstrated there are some implementation details that negatively impact the efficacy for command logging.

One example is the client invocation of ak.ones() results in three separate client server calls, none of which are called ones:

Looking at the ak.ones code, the invocations are as follows:

1. create the pdarray via
2. fill with ones via pdarray.fill(1)
3. pdarray.__repr__ to display back to the client

In another example, ak.unique starts with the unique command which is followed by multiple delete commands deleting intermediate arrays along with a call to __repr__:

A possible enhancement would be to log all commands as submitted by the user via the client. One approach satisfies one of the command logging use cases--namely, to capture all commands within a workflow for later use in a non-interactive setting such as as cron job--is to generate and capture the command history within the Python client. Longer-term, being able to precisely capture solely user-specified commands server-side will require additional message metadata and processing logic. However, this issue is designed to satisfy the above-mentioned use case.

[hokiegeek2]

Testing within Python REPL looks good:

[hokiegeek2]

Looks good within Jupyter notebook:

[hokiegeek2]

Looks good within ipython notebook: