Explore switching from `pyppeteer` to `playwright-python`

# 💡 Summary #

We should consider switching the browser interaction package we use from [pyppeteer] to [playwright-python].

## Motivation and context ##

According to the [pyppeteer] README:

> Attention: This repo is unmaintained and has been outside of minor changes for a long time. Please consider [playwright-python](https://github.com/microsoft/playwright-python) as an alternative.

Reliance on unmaintained packages can result in undesirable situations such as breaking behavior that is unlikely to be fixed and feature stagnation.

## Implementation notes ##

As this is an entirely different tool functionality will have to be verified to ensure a similar experience.

## Acceptance criteria ##

How do we know when this work is done?

- [ ] Switching packages is found to be viable.
- [ ] We switch to using [python-playwright].
- [ ] We update [cisagov/vdp-scanner-docker](https://github.com/cisagov/vdp-scanner-docker) to use the new release.

[playwright-python]: https://github.com/microsoft/playwright-python
[pyppeteer]: https://github.com/pyppeteer/pyppeteer

Start by reviewing the current pyppeteer integration and comparing its behavior with playwright-python. Verify whether the switch is viable, update the package to use the new browser tool, and check the release integration with cisagov/vdp-scanner-docker. Done means the package is switched and the dependent repository uses the new release.

Written by the indexing model from the issue text.