fix: preserve input order in WorkerPool.map() by replacing as_complet…

[rashmikandadka]

Fixes #1

Problem

as_completed() returns futures in completion order, not submission order.
This caused WorkerPool.map() to return results misaligned with input items.

Fix

Replaced as_completed() loop with ThreadPoolExecutor.map() which preserves
input order by design.

Test

Updated test_worker_pool_maps_items to assert strict ordering (removed the
sorted() workaround that was masking the bug).

[jmestwa-coder]

One small suggestion before merge: could you also add a timing-based regression test similar to the reproduction scenario from the issue? That would help permanently validate ordering preservation under varying task completion times.

Other than that, the change looks good.

[rashmikandadka]

Hi, I have added the timing-based regression test as suggested.
The new test test_worker_pool_preserves_order_with_varying_times
simulates varying task completion times and verifies that the output
order matches the input order. Please review!

[jmestwa-coder]

@rashmikandadka

Squash these into a single commit with a clean Conventional Commits message, then force-push to the same branch.

[rashmikandadka]

Hi, I have squashed the commits into a single clean commit
and force-pushed to the branch. Please review!

[jmestwa-coder]

LGTM, thank you! Merging.

[jmestwa-coder]

Thank you for your contribution.

The submitted fix has been reviewed and merged successfully. You have successfully completed this evaluation task and have been shortlisted for the next round of the selection process.

Please send the following details to hr@digiscrypt.com for verification purposes:

• Pull Request link
• Merged commit link