Data Table Limit copy clarified

Users were misinterpreting the "Limit" setting in the Data Table node, assuming it applied globally when it actually constrained results per incoming row. This naming ambiguity led to unexpected behavior that required workarounds or reconfiguration.

The setting has been renamed to "Limit Per Input Row" in both the row retrieval and table listing operations. The change makes the behavior immediately clear: each input row generates up to the specified number of results, rather than the node returning a global cap across all inputs.

This matters for workflow predictability. Users building automations that process multiple input rows now understand exactly how many output rows to expect. The clarification removes guesswork and reduces support friction around a commonly-used node. The adjustment lives in the nodes-base package where the Data Table node is defined.