[WIP] feat: add ORA filter for student_view rendering intervention

[mariajgrimaldi]

Description

This PR adds a filter meant to be used before rendering the student_view for the ORA Xblock. Here's a list of use cases we have in mind for this kind of filter:

• By accessing the block data from the template context -- data like the assessment response or files uploaded, we could check the assessment for plagiarism, correctness, etc with a 3rd party service
• We could also change prompts dynamically depending on a student's attribute
• By altering the context and the ORA template, we can change ORAs base design if we want to
  The idea is to have access to the block status in a moment in time so we can externally access it.

The specific use case we're implementing with this filter is:

As a professor or student, I want to check my essay with an external service like Turnitin for plagiarism.

This is how I imagine the use case implementation:

How to test

This is a proof of concept, so testing it can be wacky. Here's a list of steps you can follow so you can test the ongoing implementation:

1. Install the needed libraries:

pip install git+https://github.com/openedx/openedx-filters.git@MJG/ora-student-view-filter
pip install git+https://github.com/eduNEXT/edx-ora2.git@MJG/ora-student-view-filter
pip install git+https://github.com/eduNEXT/platform-plugin-turnitin.git@MJG/turnitin-pipeline-step

2. Add the following configuration:

    OPEN_EDX_FILTERS_CONFIG = {
      "org.openedx.learning.ora.student_view.render.started.v1": {
          "fail_silently": False,
          "pipeline": [
              "platform_plugin_turnitin.extensions.filters.CheckTurnitinForPlagiarism",
          ]
      },
    }

3. Restart services
4. Configure an ORA block for text submissions
5. Submit your assessment

References

Turnitin: https://www.turnitin.com/

[openedx-webhooks]

Thanks for the pull request, @mariajgrimaldi! 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.

This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

[mphilbrick211]

Hi @mariajgrimaldi! Are you still planning to pursue this, or can we close it?

[mariajgrimaldi]

@mphilbrick211: thanks for the reminder! I'll close this for the time being