feat(utils/async/any-by): add instrumentation to measure async operation duration

[MANDEep22332]

Resolves #5808

Description

What is the purpose of this pull request?

This pull request:

• {{TODO: Adds a high-resolution timer (instrument.js) to the anyByAsync utility to
  measure the duration of async operations. The timer starts when anyByAsync
  is invoked and stops when the done callback is called, returning elapsed
  time in milliseconds. }}
  ##changes
• internal/instrument.js: new file — creates a high-resolution timer using
  process.hrtime() and returns elapsed time in milliseconds
• lib/factory.js: integrate createTimer into anyByAsync; duration is
  passed as a third argument to the done callback
• test/test.instrument.js: unit tests for the createTimer function

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.

• Duration is forwarded to the caller via done( error, bool, duration )
  rather than logged, keeping the utility side-effect free
• No changes to the public API of anyByAsync.

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

[kgryte]

This change is unrelated to this PR.

[kgryte]

@MANDEep22332 This PR is not what we are looking for in terms of instrumentation. See the upstream RFC in the GSoC repo: stdlib-js/google-summer-of-code#9. As such, I am going to go ahead and close this PR.

Thank you for your interest, and we look forward to your future contributions.