Separate example_scripts testing from unit_testing

[jpolton]

Perhaps:

• unit_testing is a requirement for committing to develop
• example_scripts testing is a requirements for committing to master

Example scripts have two (three?) types:

• Can be run with example_files
• Can not be run with example_files
• No data dependency?

Story: Seeking advice on how to structure the workflow that ends up with working code on master.

Aug Update We are moving example_scripts/*py to notebooks.ipynb Is there a workflow to verify these still work before a push to master?

[thogar-computer]

Developer input on how testing and testing workflow might be setup for easier work (scalable) - This can be done via a meeeting

[lukegorman]

maybe pick this up tomorrow

[jpolton]

example_scripts are physically removed from unit_testing
example_scripts/notebooks are tested during the documentation build.
Component functionality is tested during component testing.
A new issue to map notebook testing GitAction from COAsT-site to COAsT: Issue 552