Run continuation asynchronously in context of events

[nvborisenko]

This PR make Playwright events waiter more friendly with sync-over-async pattern.

Issue

This piece of code demonstrates deadlock. Real code, you can run it (I ran it in NUnit).

await page.RunAndWaitForResponseAsync(async () =>
{
    await page.GotoAsync("https://linked.in");
}, new Regex(".*google.*"));

//await Task.Yield();

Task.Run(async () => await page.Locator(".nav__logo-link").ClickAsync()).GetAwaiter().GetResult();

Here GetAwaiter().GetResult() is blocked. We understand that it is anti-pattern, sync-over-async. To fix it we can add await Task.Yield(). But what if Playwright can be more friendly for dummy users like me?

Solution?

This PR allows tasks continuations asynchronously. Now the code above just works.

[nvborisenko]

Apologies for the inquiry, but after a month without activity, I'm concerned I may have done something improperly. @mxschmitt, if you happen to know the cause, I would be very grateful for a hint. Thank you.

[Skn0tt]

Hi Nikolay, sorry for not taking a look earlier. I'll ask our colleague Dima for a review, but it'll take a little longer due to holidays.

[Skn0tt]

I did some digging on the ramifications of this options, and it seems like a safe change for us. The only negative implication is a slight overhead since the continuation now needs to wait for the scheduler, but that microsecond impact is neglegible given we're dealing with slow browsers.

My understanding of DotNet's async scheduling is limited, so please take another look @dgozman.

[nvborisenko]

It is absolutely safe, moreover it is recommended for libraries to prevent deadlocks I demonstrated in the original issue.

[dgozman]

The fix looks good to me. Let's add a test though, to avoid regressing this behavior.