Adds ConfigureAwait(false) to all await statements

[santisq]

When an asynchronous method awaits a Task directly, continuation usually occurs in the same thread that created the task, depending on the async context. This behavior can be costly in terms of performance and can result in a deadlock on the UI thread. To avoid these problems, call Task.ConfigureAwait(false). For more information, see ConfigureAwait FAQ.

[codecov]

Codecov Report

Attention: Patch coverage is 95.12195% with 4 lines in your changes missing coverage. Please review.

Project coverage is 96.47%. Comparing base (c972bf5) to head (91e7fc2).
Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
...ParallelPipeline/Commands/InvokeParallelCommand.cs	77.77%	1 Missing and 1 partial ⚠️
src/PSParallelPipeline/RunspacePool.cs	91.66%	0 Missing and 1 partial ⚠️
src/PSParallelPipeline/Worker.cs	93.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   97.01%   96.47%   -0.55%     
==========================================
  Files          12       12              
  Lines         502      510       +8     
  Branches       32       35       +3     
==========================================
+ Hits          487      492       +5     
- Misses         10       12       +2     
- Partials        5        6       +1     

Flag	Coverage Δ
PS-5.1	96.75% <95.12%> (-0.70%)	⬇️
PS-7_Linux	96.47% <95.12%> (-0.55%)	⬇️
PS-7_Windows	96.75% <95.12%> (-0.70%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.