Add propelcode test conditions in score/evaluation

[devendrapat]

Notes for Reviewer

Pre-Review Checklist for the PR Author

• PR title is short, expressive and meaningful
• Commits are properly organized
• Relevant issues are linked in the References section
• Tests are conducted
• Unit tests are added

Checklist for the PR Reviewer

• Commits are properly organized and messages are according to the guideline
• Unit tests have been written for new behavior
• Public API is documented
• PR title describes the changes

Post-review Checklist for the PR Author

• All open points are addressed and tracked via issues

References

Closes #

[propel-code-bot]

Add evaluation scenarios, build targets, and guides under score/evaluation

This PR introduces a comprehensive evaluation suite under score/evaluation, adding multiple category-specific headers that intentionally embed review issues, plus an aggregate evaluation_all binary to compile all scenarios together. It also adds a deliberately flawed unit test suite and per-directory EVALUATION_GUIDE.md files to document expected findings, along with Bazel BUILD targets and aliases to expose each scenario.

This summary was automatically generated by @propel-code-bot