Refactor: introduce 2 associated functions to PipelineData (#16233)

# Description
As title: this pr is try to introduce 2 functions to `PipelineData`:
1. PipelineData::list_stream --> create a PipelineData::ListStream
2. PipelineData::byte_stream -> create a PipelineData::ByteStream
And use these functions everywhere.

### Reason behind this change
I tried to implement `pipefail` feature, but this would required to
change `PipelineData` from enum to struct. So use these functions can
reduce diff if I finally change to struct. [Discord message
here](https://discord.com/channels/601130461678272522/615962413203718156/1396999539000479784)
is my plan.

# User-Facing Changes
NaN

# Tests + Formatting
NaN

# After Submitting
NaN

crates/nu-lsp/src/lib.rs

@@ -531,7 +531,7 @@ mod tests {
                 engine_state,
                 stack,
                 &block,
-                PipelineData::Value(Value::nothing(Span::unknown()), None),
+                PipelineData::value(Value::nothing(Span::unknown()), None),
             )
             .is_ok()
         );