NDV components migrated away from direct workflowObject access

The NDV (Node Detail View) layer is stepping back from direct access to the legacy workflowObject. Three files in the editor UI — the NDV store, the ParameterInputList component, and the NodeSettings component — have been updated to query data through the workflowDocumentStore facade instead. A new getParentNodes method was added to the workflowDocumentNodes module to bridge the gap.

This matters because n8n is laying groundwork for CRDT, and the old workflowObject won't be the source of truth forever. By routing all NDV reads through a consistent facade now, the team avoids a bigger migration later. The pattern is straightforward: swap workflowObject for workflowDocumentStore?.value, handle optionals properly, and use getNodeByName instead of getNode. The NodeSettings component also picked up a simpler reference — using workflowId directly rather than digging into workflowObject.id.

The NDV store changes are small but symbolic: parent node lookups now return false on failure instead of throwing, a small but meaningful robustness improvement.