Bump @playwright/test to 1.60 to fix UI e2e install hang on Node 24+

[choo121600]

Bumps @playwright/test in airflow-core/src/airflow/ui from 1.58.2 to 1.60.0 to fix a hang during playwright install in the UI e2e CI job on GitHub-hosted runners.

Why

The ui-e2e-tests / Run Playwright tests job hangs in the following pattern
https://github.com/apache/airflow/actions/runs/26345383001/job/77556090749

This is caused by microsoft/playwright#40724: a bug in the yauzl/fd-slicer ZIP extractor bundled by Playwright where extraction hangs after a successful download on Node ≥ 24.16.

Our workflow uses node-version: 24 (which resolves to the latest 24.x release), so it hits the bug.

The fix landed upstream and was first released in Playwright v1.60.0 on May 11.

Change

• airflow-core/src/airflow/ui/package.json
  • @playwright/test ^1.58.2 --> ^1.60.0
• airflow-core/src/airflow/ui/pnpm-lock.yaml
  • regenerated; only @playwright/test, playwright, and playwright-core were updated to 1.60.0

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker dd8c60e v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.