Remove ConfigureAwait from test code for consistency

[Copilot]

Description

Removed all ConfigureAwait(false) calls from test code in ChunkAsyncTests.cs. The .editorconfig disables S3216 for tests, indicating ConfigureAwait is unnecessary in test scenarios.

Changes:

• Removed .ConfigureAwait(false) from enumerator.MoveNextAsync() in cancellation test (line 143)
• Removed .ConfigureAwait(false) from Task.Delay() in CreateDelayedSource helper (line 171)

Type of change

• Refactor

How Has This Been Tested?

• All 14 ChunkAsync unit tests pass on .NET 8.0
• CodeQL security scan passed with no alerts

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Screenshots (if applicable)

N/A

Additional context

This change addresses inconsistent use of ConfigureAwait in test code identified during review of #8. Test code does not require explicit synchronization context handling.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Copilot wasn't able to review any files in this pull request.