add problem data to instructor reporting

[KatelynGit]

What are the relevant tickets?

https://github.com/mitodl/hq/issues/11464

Description (What does it do?)

add problem data to new instructor reporting table

How can this be tested?

dbt build --select instructor_module_problems_report

[Copilot]

Pull request overview

Adds a new dbt reporting model to support instructor-facing reporting by exposing learner-level problem attempt data joined to course/run, course structure (section/subsection), and organization metadata.

Changes:

• Introduces instructor_module_problems_report SQL model that joins enrollments, users, problems, problem events, and course content hierarchy.
• Documents the new model/columns in src/ol_dbt/models/reporting/_reporting__models.yml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 9 comments.

File	Description
src/ol_dbt/models/reporting/instructor_module_problems_report.sql	New reporting query for learner problem attempts enriched with course structure and org/course metadata.
src/ol_dbt/models/reporting/_reporting__models.yml	Adds model + column documentation for the new reporting table.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[rachellougee]

dbt runs fine, I left two comments, both are worth addressing before merging

[rachellougee]

Can we add some tests in this new model? At minimum: not_null on user_email, courserun_readable_id, and problem_name. A unique combined key to prevent fan-out.

[rachellougee]

This left join produced a lot of empty rows where attempt, success, and grade are all null have no actionable value

[KatelynGit]

they want to see when learners don't complete problems- however I agree it's too many records I'm checking with the requestor- waiting for a reply