Feat: @inquirer/testing better handling of asynchronous action

[SBoudrias]

There's many tests within the core test suite relying on await Promise.resolve(). This is far from ideal since new async actions require more wait code; making it not super robust to refactors and code change.

I'd like to find a better way to hook into the library to detect when the code is waiting.

[Sakthieswaran-tech]

Hi I’m interested in working on this issue. May I take it on?

[SBoudrias]

@Sakthieswaran-tech go ahead. Do note this one likely involves some tradeoff in the testing library. I suggest you investigate a bit what could be done, and propose some path forward here before spending too much time cutting a clean PR (we should agree on the approach to make sure you don't waste time.)

[Sakthieswaran-tech]

Thanks! I’ll investigate the possible approaches and propose a path forward here before starting a PR.