Invalid connections are allowed when inserting include workflows with no input arguments from the toolbox

[glopesdev]

Include workflows containing no nested WorkflowInput nodes do not allow input connections from other nodes, i.e. connecting an input to a nested workflow with no declared inputs will be rejected by the editor. This is the expected behavior so the nested node works as a regular operator.

However, the editor does not honor nested WorkflowInput declarations on IncludeWorkflow nodes when inserting include extensions from the toolbox, and will allow the selected node to be connected to the newly inserted node regardless of whether the included workflow accepts inputs or not.

This is especially problematic when chaining multiple included workflows with no inputs, as the editor will try to chain them all into a single subscribe chain, when in fact what you probably want is to add them as independent nodes.