Summary panel refactor

[danielrafailov1]

Proposed Changes

(Describe your changes here. Also describe the motivation for your changes: what problem do they solve, or how do they improve the application or codebase? If this pull request fixes an open issue, use a keyword to link this pull request to the issue.)

Refactored SummaryPanel component from react-table v6 to v8

• Changed ReactTable components to Table components
• Added new imports and removed old one
• Changed criterionColumns function to use createColumnHelper
• Changed extraMarksColumns function to use createColumnHelper

Added tests

• to check that the Old Mark column doesn't show in the SummaryPanel when remark_submitted is false
• to check that the Old Mark column does show in the SummaryPanel when remark_submitted is true
• to check that the mark assigned to the user shows up in the Mark column of the SummaryPanel table
• to check that if no mark was assigned to the user then we see a dash in the place of where the mark would be
• to check that the old mark is shown when remark_submitted is true

Screenshots of your changes (if applicable)

Associated documentation repository pull request (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)	X
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have updated the project Changelog (this is required for all changes).
• I have verified that the pre-commit.ci checks have passed.
• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[coveralls]

Coverage Report for CI Build 28303297397

Coverage increased (+0.006%) to 90.251%

Details

• Coverage increased (+0.006%) from the base build.
• Patch coverage: 17 uncovered changes across 1 file (15 of 32 lines covered, 46.88%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
app/javascript/Components/Result/summary_panel.jsx	32	15	46.88%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	50871
Covered Lines:	46927
Line Coverage:	92.25%
Relevant Branches:	2419
Covered Branches:	1168
Branch Coverage:	48.28%
Branches in Coverage %:	Yes
Coverage Strength:	127.31 hits per line

---

💛 - Coveralls

[david-yz-liu]

@danielrafailov1 nice work, I just left a few minor comments

[david-yz-liu]

It was like this in the original version as well, but please internationalize this string ("Old Mark").

[david-yz-liu]

Use the parameter name props instead of info (this is more common throughout our codebase)

[david-yz-liu]

Same comment here (and the other cell definitions below)

[david-yz-liu]

Ah, so locale files under models are really only for model names, attributes, and validation error messages. Please move this to views/results instead, as that's where most of the grading UI-related strings are stored