fix(instrumentation): handle Promise-like objects as Promises

[jamietanna]

Changes

When instrumenting, we specifically handle Promises. However, if we have
an object, like SimpleGit's Response:

export type Response<T> = SimpleGit & Promise<T>;

This does not get correctly instrumented, and we end up not waiting for
the function call to complete.

We can make sure we use isPromise to correctly check if it's a native
Promise, or something with a Promise-like API.

As an alternative to #39653.

Evidence

Before (git clone immediately returns):

After (git clone returns correct timing)

Context

Please select one of the below:

• This closes an existing Issue: #
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

The public repository:

[jamietanna]

Driving this through a test was a bit awkward, and I couldn't get it passing: #39663 is where I've started this, but given running it with a repository works, I think we should merge as-is

[github-actions]

🎉 This PR is included in version 42.29.2 🎉

The release is available on:

• GitHub release
• 42.29.2

Your semantic-release bot 📦🚀