[Bug]: Used as dependency in conda-forge requires pinning `python-playwright` to same version as `playwright`

[Pijukatel]

Version

1.5x.x

Steps to reproduce

When using playwright-python as a dependency on conda-forge, I have to manually add playwright and select compatible versions of playwright and playwright-python. The failure to do so can lead to a build error like this:

Verifying transaction: ...working... ERROR:conda.stderr:
ClobberWarning: This transaction has incompatible packages due to a shared path.
packages: conda-forge/osx-64::playwright-1.57.0-hc159963_0, conda-forge/noarch::playwright-python-1.56.0-pyhcf101f3_0
path: 'bin/playwright'

The problem is that the versions published are not often the same.
See:
https://anaconda.org/channels/conda-forge/packages/playwright-python/overview
1.56.0
1.55.0
1.54.0
...

https://anaconda.org/channels/conda-forge/packages/playwright/overview
1.57.0
1.56.1
1.55.1
1.55.0
...

Expected behavior

I expect that just using playwright-python as a dependency will resolve to a compatible version of playwright.

Actual behavior

Using playwright-python as a dependency can resolve to an incompatible version of playwright.

Additional context

No response

Environment

- Operating System: [Ubuntu 22.04]
- CPU: [arm64]
- Browser: [All, Chromium, Firefox, WebKit]
- Python Version: [3.12]
- Other info:

[Pijukatel]

Raise here: conda-forge/staged-recipes#31081 (comment)

[Pijukatel]

If this issue should be reported in conda-forge/playwright-python-feedstock, please feel free to close this one.

conda-forge/playwright-python-feedstock#19