Implement "Provide ability to mark a requirement as Satisfied"

What does this MR do?

This MR implements the frontend requirements outlined in #218607 (closed) by adding the ability to manually mark a requirement as satisfied or failed.

How is requirement management done?

A requirement can have associated tests and tests can either pass or fail. Based on the lastest test report, we display either satisfied(test passed) or failed(test failed) badge. We display no badge if the requirement is neither 'satisfied' nor 'failed' (for example, it's been just created.)

In this MR, we implement the ability to manually mark a requirement as satisfied. This is internally done by creating a test report with passed status. Users may also mark a requirement as undone(neither satisfied nor failed) and we internally create a test report with failed status.

In summary:

• last test report is not found => it's neither satisfied nor failed; don't display any badge
• last test report PASSED => satisfied
  • but last test report was manually created => still satisfied
• last test report FAILED => failed
  • but last test report was manually created => a requirement is marked as 'undone' (i.e., don't display any badge, just like when it is first created).

Screenshots

Demo

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• [-] Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Issue #218607 (closed)