test: trivial README wording tweak to validate eval-assessment flow

[bryanchen-d]

Test PR for #312430 — validating the ~requires-eval-assessment eval-assessment CI flow.

Do not merge.

Plan:

1. Verify happy path by applying ~requires-eval-assessment to this PR and watching for the 5 progress comments.
2. Will use a separate PR for the failure-path test (step 13).
3. Will test benchmark override (~requires-eval-assessment swebench) on a follow-up.

[Copilot]

Pull request overview

This PR makes a trivial wording update in the repository README to validate the ~requires-eval-assessment CI flow described in #312430.

Changes:

• Rephrases “edit-build-debug cycle” to “edit, build, and debug cycle” in README.md.

Show a summary per file

File	Description
README.md	Small wording tweak in the Visual Studio Code description paragraph to support the test PR objective.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 0

[vs-code-engineering]

⏳ Queued vscode build for 4820eefb3b9125d60d80de5d02c3039ddd5bb5b2 (step 1/2).

• Build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=434137
• When this succeeds, the eval-assessment publish build will be queued automatically.

[vs-code-engineering]

❌ vscode build did not succeed (result: partiallySucceeded) — eval-assessment publish was not queued.

• Build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=434137

[vs-code-engineering]

⏳ Queued vscode build for 4820eefb3b9125d60d80de5d02c3039ddd5bb5b2 (step 1/2).

• Build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=434198
• When this succeeds, the eval-assessment publish build will be queued automatically.