Multiple additions, includes #51, #48

[jma25l]

Proposed changes

Bug fixes:

• Error when a problem is repeated within a list, the key attribute within CourseTreeElement, which needs to be unique, now includes the problem's index within the list. In order to quickly access problem_nm, an additional attribute nm has been added. Error when trying to open a problem folder in the TreeView #51
• Sometimes, a Are you sure you want to log out? pop-up appeared when the token expired.
• Fixed bug with repetetions from the same special character in problem titles.

Additions:

• Added a debug profile with the newly created mode semidevelopment, which activates debug features (such as invalidating tokens) but uses the production API.
• Implemented an analog structure to language runners for checkers in std problems. It includes a boolean which triggers a warning message if it is not implemented (or impossible to implement locally):

The format for these messages uses component warningCard.
By now, the implemented checkers are: std, elastic, elastic2. In all three PE would be flagged as wrong, making them simpler, therefore loose calls std.

• Added scored icon in the course view, as well as a message when such verdict is obtained. If verdict info is recieved, it is included (for instance, indicating that a EE is a TLE).
• Added the option to include a solution (identified by .cor rather than .inp) for custom testcases in std problems, apart from personal testing, may be useful to reveal test cases (either hint or manually by a supervisor). Those will be tested against the program an have the same behavious than official ones, including collapsing when being executed.
• Run All should include user tests. #48
• Non abstract problem_nm can be requested through the Show problem command, in such case, the specified language will be prioritized, unless another language is already open.

Required API edits regarding SC

• Include the obtained and the maximum score (if applicable) on the getSubmission endpoint and remove the placeholder in src/services/submission.ts:180
• On the getSampleTestcases, the criteria to determine whether a testcase is a sample should be includes rather than startsWith, as (mainly in scored problems) the identifier is prefixed, for instance abc-sample-1.inp. The same thing probably occurs with getPublicTestcases. This makes that some problems show no testcases, for instance: P47245_ca.

Types of changes

What types of changes does your code introduce to Appium?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have created an issue for this PR
• PR name is descriptive and uses "Fixes #xxx -" or "Closes #xxx -" prefix to auto-close the issue that your PR addresses
• I have read the Contributing Guide
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...