`JsonModuleExecute` is extremely verbose when executing remote functions

[alfredodeza]

This happens because process.check is used which logs the remote command at info level. The workaround is to set the level higher, but this would cause other useful information to be omitted.

The function docstring is logging at debug level for example. Not a good combination, and this output is overkill:

INFO:ADEZA:Running command: kubectl get pod -l component=api -n current -o name
DEBUG:ADEZA:trying to determine remote python executable with python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c which python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3