feat(any-by): add in-flight status object for observability

[MANDEep22332]

Resolves #9.

Description

What is the purpose of this pull request?

This pull request:

• Adds a status object returned by anyByAsync that allows callers to
  observe the progress of an in-flight async operation in real time.

Changes

• factory.js: anyByAsync now returns a status object instead of
  void. The object exposes three fields:
  • status — lifecycle state: 'pending', 'ok', or 'fail'
  • ndone — number of predicate invocations completed so far
  • nerrors — reserved for future error tracking
• factory.js: introduced a wrapper function around the user predicate
  to increment ndone on each completion
• factory.js: integrated with existing createTimer instrumentation,
  passing duration as a third argument to the done callback
• test/test.status.js: new test file covering:
  • initial status and ndone values immediately after invocation
  • short-circuit behaviour (only one element processed on first match)
  • full-scan behaviour (all elements processed when none match)

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• #{{TODO: add related issue number}}

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

The returned status object is mutable and updated in place as the
collection is processed, so callers can poll it at any point

• nerrors is initialised to 0 and is reserved for future use
• No breaking changes — the done callback signature gains an optional
  third duration argument consistent with the existing timer integratio

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers