refactor(tools): use asynchronous execa

[jamietanna]

Changes

Per #41062

Context

Please select one of the below:

• This closes an existing Issue: Closes #
• 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): Claude Sonnet 4.5

Refactor the tools directory to use the async version of execa` ~54k

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:

[viceice]

otherwise LGTM

[viceice]

this always throws on errors

[jamietanna]

Throws when we're doing it async? 👍

[viceice]

yes

[viceice]

this now throws on errors, please add the execa option to not throw, so we can check the result for errors

[jamietanna]

@viceice should we reject: false on all the invocations here? Or only from the exec function?