fix: node mapped twice

Summarize the changes

• fix: node mapped twice

• ValuesRow node have data and output fields refer to the same stuff in query values (1). For except between global and sharded table we applied special transformation, in which we cloned global subtree.
• Subtree cloner didn't respect DAG structure of our plan: there maybe multiple references to the same node. Instead it expected a tree. Fix that

Ensure that

• New code is covered by unit and integration tests.
• Related issues would be automatically closed with gitlab's closing pattern (Closes #1, #2).
• Public modules are documented (check the rendered version with cargo doc --open).
• (if PEST grammar is changed) EBNF grammar reflects these changes (check the result with railroad diagram generator.

close #762 (closed)

Next steps

• Cherry-pick to: none
• Update sbroad submodule in picodata/picodata.
• (if EBNF grammar is changed) create a follow-up issue in picodata/docs.