fix: increase item_id max lenght from 128 to 255 for peer, staff and studenttraining workflows

[vunguyen-dmt]

TL;DR - [ A short summary of what this PR does and why ]

The current max length for item_id fields of peerworkflow, staffworkflow and studenttrainingworkflow is 128 characters which are insufficient for course_id with a length greater than 70 characters. This PR alters the max length of item_id from 128 to 255.
Related forum post

What changed?

• Increase item_id max length of peerworkflow, staffworkflow and studenttrainingworkflow from 128 to 255.

Developer Checklist

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

Testing Instructions

1. Check if the definitions of these fields are varchar(255). openedx.assessment_peerworkflow.item_id, openedx.assessment_staffworkflow.item_id and openedx.assessment_studenttrainingworkflow.item_id.
2. Create a new course with an ID > 70 characters.
3. Create an Open Response component that has Student training and Peer and Staff steps.
4. Submit responses and assess them.

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

[openedx-webhooks]

Thanks for the pull request, @vunguyen-dmt! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[vunguyen-dmt]

Hi @pomegranited I messed up my commit a bit. I closed #2183 and create this new PR.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.03%. Comparing base (8de0eaf) to head (bed4e38).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2188   +/-   ##
=======================================
  Coverage   95.03%   95.03%           
=======================================
  Files         191      191           
  Lines       21003    21003           
  Branches     1896     1896           
=======================================
  Hits        19960    19960           
  Misses        779      779           
  Partials      264      264           

Flag	Coverage Δ
unittests	95.03% <100.00%> (ø)

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.

[pomegranited]

This change works as expected, thank you @vunguyen-dmt !

So that I can create a new release, could you please update the version string from 6.4.0 to 6.5.0 in these files:

• openassessment/init.py
• package.json

👍

• I tested this on my devstack by running migrations, then using previously-created ORA2 blocks, and creating new ones. Everything works as expected.
• I read through the code
• I checked for accessibility issues N/A
• Includes documentation N/A
• User-facing strings are extracted for translation N/A

[vunguyen-dmt]

@pomegranited I've updated it.

[pomegranited]

@vunguyen-dmt Oh no, the dreaded commit lint error again ☹️ See OEP-51 Conventional commits for info.

Also, there's a quality issue with e6af99c -- there needs to be a newline at the end of that file.

So you'll need to repair those commits and force push to replace them in this PR. Sorry about that!

Let me know if you have any trouble with this?

[vunguyen-dmt]

@pomegranited I've made some changes, please help to check if there are still any issues.

[openedx-webhooks]

@vunguyen-dmt 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[pomegranited]

Thank you for your contribution, and for working through the CI issues @vunguyen-dmt !