feat(ai_eff): AI Effort Prediction web changes

[SteveDala]

Background and Context

Currently, the task definition object contained a weighting field which, when populated, assisted students in understanding how much of their unit they had completed by finishing the task. This measure is implemented in a visualisation called the Progress Burndown Chart:

Unfortunately, weighting is not always filled out accurately or at all by tutors when creating task definitions. This leads to the chart feeling bad for students by way of inconsistency; sometimes submitting a Pass task reduces this Burndown chart by the same amount that a Distinction task does, even if much more effort was put into the distinction task.

The AI effort prediction feature aims to solve this task effort evaluation with an intelligent regressor trained on data from previous Task Definitions in OnTrack.

Description

This pull request introduces the necessary front-end changes to introduce intelligent effort prediction of tasks to OnTrack.

• changes the weighting field throughout the repo to estimated_hours to give meaning to the integer value in the task definition
• introduces the TaskDefinitionEffortComponent component to the Task Definition editor along with the required Typescript logic to run a prediction, get the value from the Task Definition object, and allow manual setting of the field

• adds references to the predicted_effort value stored in the Rails app and the API URL for sending prediction job requests to Sidekiq
• changes the reference variable used by the Task Burndown Chart logic (src/app/api/models/project.ts) to predicted_effort from weighting
• adds a (currently unfunctioning) toggle to the Unit Details page to allow predictions at the unit level

Dependencies

Depends on the changes to the API in doubtfire-api PR95. Successful testing depends on the ML Service defined in doubtfire-deploy PR37.

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

TODO

Testing Checklist:

• Tested in latest Chrome
• Tested in latest Safari
• Tested in latest Firefox

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have requested a review from @macite and @jakerenzella on the Pull Request

[jtalev]

Looks good, good start!

[officialid130-13e13]

Thanks for wiring the FE to the new FastAPI/Sidekiq flow. I walked through the changes and the integration points look clean.