Test/playwright test scenarios handler

[Luisdzc]

Description

We are creating a new main QA branch (Ui-playwright) which includes Playwright library and Cucumber BDD to handle and define our e2e tests scenarios although this branch keeps the old Cypress tests.

Any change has been made to the existing explorer code, this branch contains the last changes from main branch and the content of the playwright POC branch.

Checklist before requesting a review

Issue ticket number and link

• This PR has a valid ticket number or issue: [link]

Testing & Validation

• This PR has been tested/validated in Chrome, Firefox, Safari and Brave browsers.
• The code has been tested locally with test coverage match expectations.
• Added new Unit/Component testing (if relevant).

Security

• No secrets are being committed (i.e. credentials, PII)
• This PR does not have any significant security implications

Code Review

• There is no unused functionality or blocks of commented out code (otherwise, please explain below)
• In addition to this PR, all relevant documentation (e.g. Confluence / README.md file) and architecture diagrams (e.g. Miro) were updated

Design Review

• If this PR contains changes to the UI, it has gone through a design review with UX Designer or Product owner.
• In case PR contains changes to the UI, add some screenshots to notice the differences

---

Chrome

Before

After

Safari

Before

After

Responsive

Before

After