Fix #501: Add PrecedenceConstrainedScheduling model

[zazabap]

Summary

• Add PrecedenceConstrainedScheduling satisfaction problem model (Garey & Johnson A5 SS9)
• Unit-length tasks with precedence constraints, m processors, deadline D
• Satisfaction problem: does a valid schedule exist?

Fixes #501

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.28%. Comparing base (f4e5c47) to head (7fc1a97).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #626      +/-   ##
==========================================
+ Coverage   97.26%   97.28%   +0.01%     
==========================================
  Files         316      318       +2     
  Lines       41058    41232     +174     
==========================================
+ Hits        39937    40111     +174     
  Misses       1121     1121              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zazabap]

Implementation Summary

Changes

• src/models/misc/precedence_constrained_scheduling.rs — New model: satisfaction problem for scheduling unit-length tasks on m processors by deadline D with precedence constraints
• src/unit_tests/models/misc/precedence_constrained_scheduling.rs — 12 unit tests: basic, evaluation (valid/invalid/edge cases), brute force, serialization
• src/models/misc/mod.rs — Register module and re-export
• src/models/mod.rs — Add to top-level re-exports
• problemreductions-cli/src/dispatch.rs — Add load_problem and serialize_any_problem dispatch arms
• problemreductions-cli/src/problem_name.rs — Add lowercase alias resolution

Deviations from Plan

• Added input validation: num_processors > 0 and deadline > 0 assertions when num_tasks > 0 (quality review finding)
• Used 0-indexed time slots {0, ..., D-1} instead of issue's 1-indexed {1, ..., D} — standard representation choice

Open Questions

• Complexity string uses brute-force bound "deadline ^ num_tasks". No well-known refined exact algorithm exists for general PCS with variable m.
• Paper entries (display-name + problem-def) deferred to separate PR.

[GiggleLiu]

Autonomous project-pipeline stopped here because this resumed PR is now stale against main and GitHub reports it as merge-conflicting (mergeable=CONFLICTING). Handing off to Final review for human triage rather than forcing a large conflict repair inside the pipeline.

[GiggleLiu]

Complexity string uses brute-force bound "deadline ^ num_tasks".
No well-known refined exact algorithm exists for general PCS with variable m.
Paper entries (display-name + problem-def) deferred to separate PR.

I do not think these two problems are acceptable. Also, this PR does not have copilot review comments. I will move it back to final-review.