feature: authors can set cooldown periods for learner attempts

[arora-r]

PR Description

Resolves issue #17

Overview:

Type of Issue:

• Feature (feat): New functionality or feature added.
• Bug Fix (bug): Issue or bug resolved.
• Chore (chore): Maintenance, refactoring, or non-functional changes.
• Documentation Update (doc): Documentation improvements or additions.

Change Type:

• Major: Significant changes that introduce new features, large refactoring, or breaking changes. Requires thorough review and testing.
• Minor: Small to medium changes, such as adding new functionality that is backward-compatible or minor refactoring. Moderate review needed.
• Patch: Bug fixes, small tweaks, or documentation updates. Light review is sufficient.

Testing & Validation:

• Unit Tests: Added/updated to cover new logic or edge cases.
• Integration Tests: Updated to verify interactions between components.
• E2E Tests: Performed end-to-end testing in staging or development environment.
• Manual Testing: The changes were manually tested and validated.
• No Regressions: Verified that no existing functionality is broken.

Purpose:

This PR handles adding the ability for admins to set cooldown periods.

Context:

#17

Basic Usage:

Admins can set a cooldown period and when the period starts (after a certain amount of attempts). Once this threshold is reached for learners, they will have to wait a cooldown period to re-attempt an assignment.

Notes to Reviewer:

[MmagdyHafezZ]

LGTM