2.03 lab needs to be revised

[Dan-TEALS]

Lab 2.03 needs a complete revision.

• The two code tracing problems (examples 1 and 2) don't make any sense because the flow of execution depends on user input that isn't provided in the examples (and exhaustively providing inputs for each conditional branch would require at least three traces for example 1 and at least nine for example three - not considering issues of case in the comparison).
• Input string formatting is inconsistent in the two examples
• String formats don't follow PEP-8 recommendations
• The triangle program requires more scaffolding (don't expect the students to know the tests for various types of triangles off the top of their head)
• Pseudocode or a flowchart to replace the Snap! example code would be helpful for the triangle program
• The bonus is out of place since lists aren't introduced until lesson 4