Parse output labels automatically

[liamhuber]

Closes #717

First, this makes it easier to define new nodes, since there will just be less to write. Second, this will let us free up *args in Function(Node) to be used for providing input data (as discussed in #769). We'll still allow explicitly providing different output labels, but this becomes an optional kwarg instead of mandatory args.

Best-practice becomes to give good variable names to all the return values in your wrapped function, but Sam's parser is super generic and you'll still be able to access weirdly-named nodes with ["node name"] even if they're not dot-accessible. (At least that's the plan!)

• Implement and test the function return value parser from @samwaseda in Workflow: Automatic parsing of outputs #717
• Use the parser for Function(Node) and its children
• Update all the examples and docs

[github-actions]

👈 Launch a binder notebook on branch pyiron/pyiron_contrib/parse_output_labels

[github-actions]

Pull Request Test Coverage Report for Build 5578967633

• 83 of 83 (100.0%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.4%) to 13.352%

---

Totals
Change from base Build 5578949334:	0.4%
Covered Lines:	1940
Relevant Lines:	14530

---

💛 - Coveralls

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB