views: checks requests tab templates

[ptamarit]

❤️ Thank you for your contribution!

• Fixes checks: add checks tab (community curator can't easily see in a request if there are failing checks) zenodo/zenodo-rdm#1133
• See linked issue for description and screenshot

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect on Discord.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[ptamarit]

The backend sanitization and the React conterpart in the form are implemented in zenodo/zenodo-rdm#1135

[kpsherva]

why not use it directly?

Suggested change

	{%if rule_result.success %}
	{% set ns.rule_severity_level = "success" %}
	{% elif rule_result.level == "info" %}
	{% set ns.rule_severity_level = "warning" %}
	{% elif rule_result.level == "error" %}
	{% set ns.rule_severity_level = "error" %}
	{% else %}
	{% set ns.rule_severity_level = "unknown" %}
	{% set ns.rule_severity_level = rule_result.level %}

[ptamarit]

It's not super obvious, this is why I'm explaining it in the comment above:

    This code depends on 2 fields of each `rule_results` : `success` and `level`.
    If the boolean `success` field is true, it means that the check was successful.
    Otherwise, it means that the check failed, and we display the severity `level` of the check.

[kpsherva]

this part should be computed on the backend in the CheckRun

[ptamarit]

I'm running out of time, so I added a FIXME for now :(

[ptamarit]

Just auto-squashed before merging.