[Application] Improve multi-scenario comparison UX

[SilverSupplier]

Summary

• Improve batch comparison defaults so 1-8 completed scenarios are selected together by default, while larger result sets start with baseline, current, then result order up to 8 comparisons.
• Add explicit Compare panel controls for Select All, Baseline + Current, Clear, plus a Comparing X / N status label; empty comparison selection now keeps the existing empty graph/table state.
• Make comparison graph legends tolerate more scenarios with a larger palette, wrapped/elided legend labels, and overflow text.
• Clarify Run screen status copy so batch execution shows Running N scenarios and Batch X / N complete separately from the selected scenario.
• Prevent stale cached result artifacts from opening during Run Again; the result button now waits for the new batch to complete before showing comparison results.

Related Issue

• None (application-only PR)

Area

• Engine
• Domain
• Application
• Docs
• Build
• Analysis
• Chore

Architecture Check

• I kept the dependency direction application -> domain -> engine.
• I did not add Qt UI code to src/domain.
• I did not add domain or application dependencies to src/engine.
• I used src/ as the include root.

Verification

• cmake --preset windows-debug
• cmake --build --preset build-debug
• ctest --preset test-debug
• cmake --build --preset build-no-app-debug
• ctest --preset test-no-app-debug
• cmake --build --preset build-debug --target safecrowd_app
• Manual UX: launched safecrowd_app; multi-scenario Remaining graph no longer reopens stale rerun results.
• Not run (reason below)

Risks / Follow-up

• 9+ scenario saved/mock result sets still need a focused manual pass for default cap, Select All, and legend overflow behavior.

[learncold]

main 브랜치에 직접 반영되어 이 PR을 닫습니다. 반영된 최신 커밋: 6143306.