Description

Originated from kedro-org/vscode-kedro#140

%load_node works great but it doesn't work on MemoryDataset, I don't save every node and it's not easy to figure out which nodes I need to run again to produce the data

Context

• This is much more powerful because not every node has persisted data and this limited the usage of the feature.
• This enable much more powerful slicing feature in kedro-viz, which is currently limited because we do not want the slicing generate a command that Kedro does not know how to run.
• Same as above, if we are able to support more flexible slicing, we may end up expanding the API of kedro run as well since we can support different combinations of slicing

Possible Implementation

Check out the suggest_resume_scanerio in SequentialRunner:

This roughly has the logic to resume pipeline but it's hidden in a private API, we need to surface this for more generic usage.