feat: expose proctoring provider capability flags in instructor v2 API

[Anas12091101]

Description

Adds two provider-capability flags to the instructor v2 proctoring_settings endpoint so the
instructor dashboard MFE can decide whether to show the Student Onboarding Status and Review
Dashboard special-exam sections:

• supports_onboarding — wraps edx_proctoring.api.does_backend_support_onboarding(provider)
• review_dashboard_available — wraps edx_proctoring.api.is_backend_dashboard_available(course_id)

Both are computed in a small shared helper used by the endpoint's GET and PATCH. This is the same
information the legacy instructor dashboard used server-side (show_onboarding / show_dashboard in
_section_special_exams), now exposed via the v2 API. No proctoring logic is reimplemented — these
are thin wrappers over existing edx-proctoring helpers.

Impacted user roles: Developers consuming the v2 API (two new read-only boolean fields);
Operators indirectly (the MFE gates UI on these). No behavior change for learners.

Closes #

Supporting information

• Consumed by the frontend-app-instructor-dashboard PR feat: add Student Onboarding Status and Review Dashboard to Special Exams frontend-app-instructor-dashboard#219
• Internal tracking: https://github.com/mitodl/hq/issues/11865
• API spec updated: lms/djangoapps/instructor/docs/references/instructor-v2-special-exams-api-spec.yaml.

Testing instructions

1. GET /api/instructor/v2/courses/{course_id}/proctoring_settings as course staff.
2. For a course whose proctoring backend supports onboarding / a review dashboard, confirm the
   response includes "supports_onboarding": true and/or "review_dashboard_available": true.
3. For a course on the null backend, confirm both are false.
4. Run: pytest lms/djangoapps/instructor/tests/views/test_special_exams_api_v2.py::ProctoringSettingsViewTest

Other information

• Additive, backward-compatible: two new response fields, no changes to existing fields, no migrations.
• is_backend_dashboard_available inspects the course's active exams; cost is comparable to the
  existing course-wide special-exam endpoints.

[openedx-webhooks]

Thanks for the pull request, @Anas12091101!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.