feat: Add playwright tests on content system

[muhammad-ali-pk]

Done

• test auth flow
• test projects are loaded and visible
• test page removal flow
• test page change request flow
• test page creation and submission flow
• clean up jira tasks after tests
• add workflow for playwright testing

QA

QA steps

• Create a new branch from this branch and raise a PR to merge your branch to this branch
• This will trigger the playwright actions on your PR
• Verify all the actions are successful.

Please note
Make sure to remove/disregard/reject Jira tasks created as a result of running tests. In the near-future, we will automate this cleaning up process after tests
The jira tasks are now automatically cleaned up (rejected and parent unlinked) after the tests so you don't have to do that manuallly.

Fixes

• Fixes WD-20422

[webteam-app]

Demo

Jenkins

demos.haus

[immortalcodes]

Looks Good. Tests have been passing on github workflow, I am still facing issues with getting them running locally, but I guess we can go ahead with this as an initial step.
That said, the .env file has to be sourced separately now, which was not case previously for dotrun.
Thanks for the great work and patience on this task. 😃

[immortalcodes]

I am curious, what token did we use here, I am guessing it's not a personal GH token?

[muhammad-ali-pk]

@immortalcodes Good question! The github action runner automatically adds a secret named GITHUB_TOKEN that is accessible in workflow using secrets.GITHUB_TOKEN. Therefore, we don't need to pass our own personal GH token when cloning repos.

[muhammad-ali-pk]

Thanks for testing and approving @immortalcodes. We can connect to figure out the issues you're facing in your local environment.

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀