The refresh model in the staff grading form changed.
Also add a "scrollToTop" call when continuing grading.

TNL-3870

Full staff grading UI

Includes fixing my previous work on the staff assessment test to
use the required flow, not the override. Also refactors full workflow
tests and adds a new one to include a required staff grading step.

Part 2 (TNL-3493)

TNL-3493

Minor doc tweak

Per offline conversation with @catong, changing some wording in the
user visible string for editing ORA assessment steps.

Doc updates staff grading in Studio

Updating a user-facing string to include staff grading. Also updating
some dangerously outdated documentation in code that was unearthed
during PR review.

Able to enable full staff grading from studio, save without errors, and view
the staff grading step as expected from LMS.

Includes:
    -template additions, staff grading disabled by default
    -fetching real staff requirements
    -javascript to hook into the python backend
    -changing some default assumptions about assessment types
    -modifications to validation
    -small bugfix for scroll behaviorwith validation alert.
    -updates to existing unit tests
    -additional validation, serialization, and javascript tests
    -fix for staff requirements bug (no more duble-unpacking)
    -updates the bundled studio js file
    -moving StaffWorkflow initilization to api's on_init() method
    -acceptance tests (lms)
    -addition of "Staff Assessment Section" to test course for bokchoy tests
    -renaming `requirements` to `<type>_requirements` in assessment apis

TNL-3889

TNL-3465

TNL-3819

Previously, api.update_from_assessments() would call model.
update_from_assessments(), then api._serialized_with_details(reqs), which
would duplicate the update work we *just* did as part of getting the
status. Now, update() and get_details() are totally seperate operations, and
_serialized_with_details() is a read-only method that does not need to have
requirements passed in.

I've also standardized student_training and peer, the two assessment types that
do *not* auto-complete on None requirements, to return False if None, and error
out if passed {}. This is to allow staff_assess to pass None to indicate
"Update thyself, if you don't depend on requirements" to the other step types.

Also adding test_requirements_changed(), to confirm that workflows are updated
when requirements change, even though thoe requirements are no longer explicitly
passed to the getter.

Fairly simple test, should help to provide some extra peace of mind.

I misunderstood what was happening in my cursory investigation earlier -
all that needs to change here is the type of exception being caught.

TNL-3464

Add a test to verify that it is working as expected.

Staff assessments can now mark workflow as being done, with proper handling
for blocking workflows (such as peer), to hide a score if the submitter
has not yet fulfilled their obligations. Includes tests.

Also contains a tiny bugfix for a previously unexecuted codepath.

This test is trying to confirm behavior when an api cannot be loaded.
It is no longer possible for an AssessmentWorkflow to have been created
without going through __init__(), so the latter part of this test is
now trying to confirm assumptions about an impossible state.

I recommend we just remove it.

TNL-3467

Even when the icon is updated to fa, nothing happens when
the icon is clicked.

TNL-3799