Ridiculous Playwright dependency issue is back

[huijing]

So it seems like every time Playwright pushes a new release, our deploy pipelines are going to bork out because the browser executable gets downloaded into a different place from where the build process expects?

We never actually solved it the last time on Netlify, and turns our Github actions also has this issue. FML.
(╯°□°）╯︵ ┻━┻

[@mdx-js/rollup] browserType.launch: Executable doesn't exist at /home/runner/.cache/ms-playwright/chromium-1080/chrome-linux/chrome

No shit, Einstein, that's because when we ran bunx playwright install --with-deps chromium, the executable was downloaded to

Chromium 119.0.6045.9 (playwright build v1084) downloaded to /home/runner/.cache/ms-playwright/chromium-1084

BIG SIGH.

[huijing]

It seems like Netlify takes a week.
For Github actions, I had to recommit with updated dependencies? Not very sure yet. Will continue to monitor the next time Playwright updates.