Update stretch for functional expectations

[sertmer]

This PR addressed issue #632

Changes Requested in Issue:

• [x] The rubric needs to be updated to expect the use of functional components, and the use of the useState and useEffect hooks to manage state and parse updates from the API.
• [x] Make it clear that a failure to participate can result in an individual failing the project, even if the project is otherwise passing
• [x] Update rubrics to use the Yes, Not Yet, Wow scale.

Changes Made:

• [x] All of the above, as well as some minor language updates

Questions:

• Seeing as students self-assess this project and do not get any written feedback, are there any changes to the way we communicate WOW or ON TRACK?
• The rubric previously had no WOW descriptions. Are the options I've provided for WOW in line with our expectations? In line with their learning goals? Should there be more of those benchmarks?
• The rubric is a LOT - do we need to cut it down, or otherwise make it feel digestible?

[sertmer]

Thanks Cass! I'll merge it in!