Ark: Jupyter: Verbose logging makes jupyter-console unusable

[lionel-]

By default (i.e. --log option not supplied) we stream log messages to stdout/stderr. This makes jupyter-console unusable when verbosity is high because jupyter-client, used by jupyter-console, launches the kernel with subprocess.Popen() without stdout capture, which causes the kernel streams to be inherited by the jupyter-console REPL process.

To fix this we could add a --log-temp option that would create log files in $TEMPDIR/ark-logs. These would be time-stamped to make it easy to find the relevant log file when debugging. Supplying both --log and --log-temp would be an error. We would supply that option by default in our kernel.json file.

[DavisVaughan]

Looks like things are pretty quiet now on Mac and Windows, I even checked the reprex from #4382 too

Probably worth looking into this at some point

D:\Users\davis-vaughan\AppData\Local\Programs\Python\Python312\Lib\site-packages\jupyter_console\ptshell.py:136: UserWarning: No lexer found for language ''. Treating as plain text.
  warn("No lexer found for language %r. Treating as plain text." % name)