Remove redundant Correctness Verification section from factorial benchmark

[Copilot]

This PR removes the redundant "Correctness Verification" subsection from the factorial benchmark scenario to streamline the benchmark instructions and eliminate duplicate verification requirements.

What Changed

Removed the following section from scenarios/factorial.md:

### Correctness Verification

1. **Base Case**: `factorial(0) = 1`
2. **Small Values**: `factorial(1) = 1`, `factorial(2) = 2`, `factorial(3) = 6`, `factorial(4) = 24`
3. **Target Value**: `factorial(10) = 3628800`

Why This Change

The removed section contained redundant correctness checks that were already comprehensively covered in multiple other sections of the document:

• TL;DR: Clearly states the target computation factorial(10) = 3628800
• Core Requirements: Specifies the exact target computation requirement
• Acceptance Criteria: Includes correctness as a pass/fail criterion
• Submission Checklist: Requires verification of the exact result
• Local Validation: Provides functional testing instructions

Impact

• Streamlined Documentation: Eliminates redundancy while preserving all essential correctness requirements
• Improved Focus: Shifts emphasis to performance verification and technical constraints as intended
• Maintained Integrity: All necessary correctness information remains available in appropriate functional contexts
• Cleaner Structure: The "Verification Points" section now focuses purely on performance aspects

The change is minimal and surgical, removing exactly 6 lines while maintaining complete document integrity and ensuring that implementers still have clear guidance on correctness requirements.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.