feat(NOJIRA-123): add Playwright visual regression test support to deploy workflow

[bobobowis]

Summary

Add support for running Playwright visual regression tests in the frontend-deploy-workflow, matching the existing functionality already available in the frontend-pr-workflow.

This enables projects using Playwright for visual regression testing (like admin-home) to run these tests as part of their production release pipeline.

Changes

New inputs

• run-playwright-visual: Enable/disable Playwright visual tests (default: false)
• playwright-visual-command: Command to run visual tests (default: 'yarn test:visual')
• playwright-visual-timeout: Test timeout in minutes (default: 20)

New job

• Job 6: Playwright Visual Tests - Runs in parallel with other test jobs

Deploy job updates

• Added playwright-visual to deploy job dependencies
• Deploy only proceeds if Playwright visual tests pass (when enabled)

Consistency with PR workflow

This implementation mirrors the existing playwright-visual job in frontend-pr-workflow.yml, ensuring consistent behavior across PR checks and production deployments.

Test plan

• Verify workflow syntax is valid
• Test with a project using Playwright visual tests (e.g., admin-home)
• Confirm tests run in parallel with other test jobs
• Verify deploy job waits for visual tests to complete
• Confirm artifacts are uploaded correctly

[gitstream-cm]

🥷 Code experts: kb-typeform

kb-typeform has most 👩‍💻 activity in the files.
kb-typeform has most 🧠 knowledge in the files.

See details

.github/workflows/frontend-deploy-workflow.yml

Activity based on git-commit:

	kb-typeform
APR	4 additions & 0 deletions
MAR	59 additions & 31 deletions
FEB	374 additions & 9 deletions
JAN	9 additions & 1 deletions
DEC	292 additions & 12 deletions
NOV

Knowledge based on git-blame:
kb-typeform: 98%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.

[bobobowis]

Note: SonarCloud is flagging run: ${{ inputs.playwright-visual-command }} and run: ${{ inputs.pre-test-command }} as potential script injection vulnerabilities.

However, this is the existing pattern used throughout this entire workflow for all command inputs (inputs.integration-test-command, inputs.unit-test-command, inputs.build-command, etc.).

For consistency, I'm keeping the same approach. If we want to fix this security warning, it should be done in a separate PR that updates all command executions in the workflow, not just the new Playwright visual job.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
1 Security Hotspot
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud