TooTallToby tutorials: unbreak and test.

[fischman]

• Unbreak the three broken tutorials (fixes Fix TTT tutorials: 23-T-24 Curved Support, 01-02-post-cap, 01-10-light-cap #848)
  • This involved a rewrite of PPP-01-10 because I already had my own solution to that one and I couldn't easily tell what was going wrong with the previous solution.
• Add assertions to all the tutorials so that non-raising means success
• Add the TTT examples to test_examples.py added recently for Examples should be kept working by being run in a test #909
• Also dos2unix'd the TTT .py files to match the rest of the codebase.

[fischman]

FYI @jdegenstein. LMK if you'd rather I not replace your PPP0110 solution (and if you have a fix in mind already).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.91%. Comparing base (bda0a6a) to head (3e8bb44).
Report is 3 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #912      +/-   ##
==========================================
+ Coverage   96.73%   96.91%   +0.18%     
==========================================
  Files          32       32              
  Lines        9434     9434              
==========================================
+ Hits         9126     9143      +17     
+ Misses        308      291      -17     

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

[fischman]

@gumyr WDYT, worth testing TTT examples as part of automated testing?

[jdegenstein]

@fischman FYI TTT examples are (sort of) tested through the benchmarking workflow (in a separate python script)

[fischman]

@fischman FYI TTT examples are (sort of) tested through the benchmarking workflow (in a separate python script)

Thanks for the heads-up, I was unaware of that before.
Seems suboptimal that the examples' code is duplicated in the tests/ subdirectory (because of the likelihood of drift as one or the other place is edited, and the other is forgotten, and also because edits must be duplicated). Also ttt-23-t-24-curved_support is missing from the test.

Do you prefer to keep the structure at HEAD, or are you suggesting I keep this PR moving forward and delete the test_benchmarks copy of the examples, or something else?
(maybe test_benchmarks should run test_examples?)