external commands get formatted tables

Describe the bug

consider the pipeline,

ps | each {$"/local/ps/($in.name)|u64|($in.pid)"} | ^cat

One would expect cat to receive lines in the form

/local/ps/{name-of-process}|u64|{pid-of-process}

Instead, nushell formats the table as if it was going to show it to a human, and then sends it on to cat. E.G.

/home/eric/proj/demoscene/views〉ps | each {$"/local/ps/($in.name)|u64|($in.pid)"} | ^head
╭─────┬──────────────────────────────────────────────────────────────────────╮
│   0 │ /local/ps//usr/lib/systemd/systemd|u64|1                             │
│   1 │ /local/ps/kthreadd|u64|2                                             │
│   2 │ /local/ps/rcu_gp|u64|3                                               │
│   3 │ /local/ps/rcu_par_gp|u64|4                                           │
│   4 │ /local/ps/netns|u64|5                                                │
│   5 │ /local/ps/kworker/0:0H-events_highpri|u64|7                          │
│   6 │ /local/ps/mm_percpu_wq|u64|9                                         │
│   7 │ /local/ps/rcu_tasks_kthread|u64|10                                   │
│   8 │ /local/ps/rcu_tasks_rude_kthread|u64|11                              │

This is pretty much entirely useless for interacting with any external command I can think of.

How to reproduce

1. pipe anything non trivial to an external command

Expected behavior

For a simple list of strings I expect each string to be sent to the external command as 1 line. To be honest, given that primitive, and the already ample string manipulation functions in nushell, you should be able to do most anything.

Screenshots

No response

Configuration

No response

Additional context

No response

Reproduce the pipeline shown in the issue, especially piping a list of strings to an external command such as ^head or ^cat. Trace the external-command boundary and determine where structured values are formatted; done means simple string lists reach the command as one unformatted line per item.