Switch to computed scores across the autopilot

[edjroz]

Description

Now that the combinatorial auction cutover (#3387) is complete, this PR fully transitions the autopilot from solver-reported scores to protocol-computed scores. The autopilot was still using Score::Solver when storing competition results, even though the actual scoring is done by the protocol. This aligns the stored score variant with reality and removes dead code from the driver.

Changes

• Switch Score::Solver → Score::Protocol in the autopilot run loop when recording solver settlements (crates/autopilot/src/run_loop.rs)
• Remove unused score field from the driver's Solved struct (crates/driver/src/domain/competition/mod.rs)
• Remove score from the driver's /solve response DTO (crates/driver/src/infra/api/routes/solve/dto/solve_response.rs)
• Mark Score::Solver and Score::ProtocolWithSolverRisk as deprecated in the enum, keeping them for backward-compatible deserialization (crates/model/src/solver_competition.rs)
• Add score_protocol_round_trip and score_solver_legacy_deserialize tests

How to test

cargo nextest run -p model score
cargo nextest run -p driver
cargo check -p autopilot

Related Issues

Should close #3415

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[gemini-code-assist]

Code Review

This pull request deprecates the Solver and ProtocolWithSolverRisk score variants in favor of Protocol within the competition model. It removes the score field from the Solved domain object and the Solution DTO, while updating the autopilot to utilize protocol-calculated scores. Additionally, unit tests were expanded to include serialization round-trip and legacy deserialization checks. No critical issues found.

[edjroz]

I have read the CLA Document and I hereby sign the CLA

[edjroz]

recheck