`tests/page/page-set-content.spec.ts:153:3 › should handle timeout properly` will infinitely loop the page
as a result, none of the WebKit inspector protocol messages are handled
`context.clearCookies` performs multiple round-trips using the WebKit inspector protocol (`Page.getCookies` and then `Page.deleteCookie` for each)
as such, give the page fixture a `timeout` so that if `clearCookies` hangs then the worker will be killed and restarted instead of waiting forever
upstream WebKit is able to send this as soon as Web Inspector is opened since that only happens when there is for sure something to inspect
as such, Web Inspector doesn't have to wait to receive a message in order to know that there is a target to receive this command
leverage `Target.targetCreated` as the likely first event from the inspected page to emulate this behavior
Yury Semikhatsky