feat: add handling for peer submission timeout / cancel

[nsprenkle]

TL;DR - Send the ERR_SUBMISSION_NO_LONGER_AVAILABLE error code and a 404 error when trying to submit a grade in the following circumstances:

1. Lease on a peer assessment has expired.
2. Submission that a student was grading has been cancelled.

JIRA: AU-1647

Developer Checklist

• Reviewed the release process
• Translations and JS/SASS compiled
• Bumped version number in openassessment/__init__.py and package.json

Testing Instructions

[ How should a reviewer test this PR? ]

Reviewer Checklist

Collectively, these should be completed by reviewers of this PR:

• I've done a visual code review
• I've tested the new functionality

FYI: @openedx/content-aurora

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (dae4b35) 94.92% compared to head (cdb98e6) 94.92%.

Files	Patch %	Lines
openassessment/xblock/ui_mixins/mfe/mixin.py	33.33%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2157      +/-   ##
==========================================
- Coverage   94.92%   94.92%   -0.01%     
==========================================
  Files         191      191              
  Lines       20571    20574       +3     
  Branches     1865     1866       +1     
==========================================
+ Hits        19528    19529       +1     
- Misses        779      780       +1     
- Partials      264      265       +1     

Flag	Coverage Δ
unittests	94.92% <60.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[jansenk]

This actually won't fix the issue, and I think the issue is different than what we think it will be anyways:

Old code:

• Pass the current submission uuid along with the assessment info
• Backend calls get_peer_whatever which discards "old" PeerWorkflowItem and grabs a new one
• passed old uuid doesn't match new uuid and assess fails

We don't pass a submission uuid back to the mfe view. What I think will happen now is:

• Call peer_assess with assessment for old submission
• Old peer workflow item is discarded and we grab a new one
• apply assessment for old submission to new submission

No bueno!! We should probably make a new ticket to address this

[nsprenkle]

Okay, will close this PR, awaiting a different fix.

This actually won't fix the issue, and I think the issue is different than what we think it will be anyways:

Old code:

• Pass the current submission uuid along with the assessment info
• Backend calls get_peer_whatever which discards "old" PeerWorkflowItem and grabs a new one
• passed old uuid doesn't match new uuid and assess fails

We don't pass a submission uuid back to the mfe view. What I think will happen now is:

• Call peer_assess with assessment for old submission
• Old peer workflow item is discarded and we grab a new one
• apply assessment for old submission to new submission

No bueno!! We should probably make a new ticket to address this