Allow stor insert and stor update to accept pipeline input

[JoaoFidalgo1403]

• this PR should close Accept pipeline input for stor insert values #11433

Description

This PR implements pipeline input support for the stor insert and stor update commands,
enabling users to directly pass data to these commands without relying solely on flag parameters.

Previously, it was only possible to specify the record data using flag parameters,
which could be less intuitive and become cumbersome:

stor insert --table-name nudb --data-record {bool1: true, int1: 5, float1: 1.1, str1: fdncred, datetime1: 2023-04-17}
stor update --table-name nudb --update-record {str1: nushell datetime1: 2020-04-17}

Now it is also possible to pass a record through pipeline input:

{bool1: true, int1: 5, float1: 1.1, str1: fdncred, datetime1: 2023-04-17} | stor insert --table-name nudb
{str1: nushell datetime1: 2020-04-17} | stor update --table-name nudb"

Changes made on code:

• Modified stor insert and stor update to accept a record from the pipeline.
• Added logic to handle data from the pipeline record.
• Implemented an error case to prevent simultaneous data input from both pipeline and flag.

User-facing changes

Returns an error when both ways of inserting data are used.

The examples for both commands were updated and in each command, when the -d or -u fags are being used at the same time as input is being passed through the pipeline, it returns an error:

Also returns an error when both of them are missing:

Tests + Formating

• 🟢 toolkit fmt
• 🟢 toolkit clippy
• 🟢 toolkit test
• 🟢 toolkit test stdlib

[fdncred]

There's already a PR for stor insert #12859

[JoaoFidalgo1403]

We understand that there is already a PR addressing this issue. However, we wanted to highlight that we have also been working on this problem for some time. We believe our PR is comprehensive and well-organized. We deeply respect the work done by others, but we would be very grateful if you could consider reviewing our contribution as well.

@fdncred Thank you for your time and consideration.

[NotTheDr01ds]

Looking at the commit, this doesn't appear to handle a table type as an input, just a record. Is that correct? into sqlite can handle table or record as input types, and, as mentioned in #11433, it would be nice to have the same semantics for both into sqlite and stor insert. I was hoping we'd just be able to re-use and share the same code-base for all related commands.

[friaes]

We actually hadn't noticed that @NotTheDr01ds. Implementing that feature would indeed be more complex and challenging for us at the moment. However, we can definitely still make stor insert/update handle table as input in a future pull request, if that wouldn't be a problem.