Fix test tutorials workflow

[lymichelle21]

Address #198

• Update test_tutorials to run every tutorial
  • Split into tests_tutorials and tests_tutorials_part_two to limit timeout issues
• Add temporary placeholder to ignore test_examples - will need to be removed as a requirement (in progress)
• Add temporary placeholder to ignore benchmarking - will need to be fixed (noted in Add benchmarking #203)

[github-actions]

Thank you for opening this PR. Each PR into dev requires a code review. For the code review, look at the following:

• Reviewer (someone other than author) should look for bugs, efficiency, readability, testing, and coverage in examples (if relevant).
• Ensure that each PR adding a new feature should include a test verifying that feature.
• All errors from static analysis must be resolved.
• Review the test coverage reports (if there is a change) - will be added as comment on PR if there is a change
• Review the software benchmarking results (if there is a change) - will be added as comment on PR
• Any added dependencies are included in requirements.txt, setup.py, and dev_guide.rst (this document)
• All warnings from static analysis must be reviewed and resolved - if deemed appropriate.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.65%. Comparing base (e7491d5) to head (68f6aca).
Report is 24 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #201   +/-   ##
=======================================
  Coverage   83.64%   83.65%           
=======================================
  Files         102      102           
  Lines       10852    10857    +5     
=======================================
+ Hits         9077     9082    +5     
  Misses       1775     1775           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kjjarvis]

This looks great. Just one question to make sure only necessary changes are checked in (I'm not sure - you know best!)