feat: add option to filter targets

[jschfflr]

This change closes #7191 by introducing a callback that can be used to decide if puppeteer should connect to a given target.

[peterbe]

I have no idea how this PR works or what the changes mean, but in the release change log for version 9.1.0 this PR is the only one in that release.
Ever since upgrading to puppeteer 9.1.0 we started seeing strange errors from jest.
Our project has a bunch of *.test.js files and only a couple of them have anything to do with puppeteer. There are a couple that use jest-puppeteer.

Unscientifically, I found that our test suite stopped being so busted when we downgraded back to puppeteer 9.0.0.
Not sure who or how it helps.

Here's my issue about it
Here's my PR to hack around it

[jschfflr]

Hi @peterbe Thanks for bringing this to my attention!
I'll try to reproduce the problem and see what this might be about.

[jschfflr]

@peterbe Thanks for pinging - I think this is related to the fact that the filter can be async. I'll verify that now...

[peterbe]

What's a "filter" :)

[jschfflr]

By default, puppeteer connects to all available targets (=pages and workers etc.). We wanted to give developers a way to control which ones to connect because puppeteer enables some CDP domains by default which might interfere with what that target is doing.
Unfortunately, I allowed the filter to be async and awaited its result. That led to a situation in which the targetInfoChanged event was processed before the target was created because it was still waiting for the return of the targetFilter.

[jribbens]

Yeah I have just raised issue #7204 which turns out to be due to this.