Additionally introduce `@playwright/browser-<browser>` packages that
just download the respective browser, but do not export anything.
References #26614.
Fixes: https://github.com/microsoft/playwright/issues/20390
We are doing such a bad job documenting these third party approaches
that they bring more harm than benefit. We should let respective
integration owners own the documentation and link to it. I'll remove it
altogether for now.
Currently, our Playwright Test and Playwright Library pages acknowledges each exist, but don't really spell out the difference between the two.
The goal with this page is:
1. Clarify which package a user should be using
2. If using Playwright Library, show what's required
Depending on the content of this page, it may be possible to make our docs completely `@playwright/test`-first (including the examples), and then just have one doc that answers "if you're using Playwright Library, here's the few unique bits to it that you didn't have to think about in Playwright Test".
The less duplication we have across Library vs. Test docs, the less room there is for confusion and maintenance burden.
@mxschmitt is going to start making the rest of the docs more test-centric once this lands.
