Turns out that I was still starting vscode with --log trace. Something I added to my vscode shortcut when I was looking at another issue. After removing it, the the trace logs in the output channel went away.