fix(testing): run playwright from workspaceRoot

[barbados-clemens]

Current Behavior

playwright runs from projectRoot, which results in paths having to be from projectRoot causing extra pathing '../../' for many options.
Also doesn't align with most other executor behaviors defining paths from the workspaceRoot.

Expected Behavior

run playwright from workspaceRoot making pathing align with other executors

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 19, 2023 6:32pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 6a2d428. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• linux nx affected --target=e2e --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c --parallel=1
• linux nx run-many -t check-imports check-commit check-lock-files depcheck check-codeowners documentation --parallel=1 --no-dte
• linux nx affected --target=build --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c --parallel=3
• linux nx affected --target=test --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c --parallel=1
• linux nx affected --target=lint --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c --parallel=3
• nx-cloud record -- nx format:check --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c
• linux nx documentation --no-dte
• macos nx affected -t e2e-macos --parallel=1 --base=4ffc68e18b5168e7395b28ac87afd6ce9d42def0 --head=6a2d42814ec5e81b1977a480af604c00f9d31c2c

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.