create e2e tests with playwright

[Naseem77]

you must use the same arch that has been used here: https://github.com/FalkorDB/falkordb-browser inside the e2e dir.
you have to run all the tests twice before you declare you have finished.

---

This repo is using Opire - what does it mean? 👇

💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #332 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Naseem77 (replace 20 with the amount, and @Naseem77 with the user to tip).

📖 If you want to learn more, check out our documentation.

[overcut-ai]

Completed Working on "Automated Ticket Triage "

✅ Initial automated triage finished for issue #332: added labels category/tests, needs-info, needs-human-triage; posted triage summary comment requesting further details; flagged for human review due to low confidence.

---

👉 View complete log

[overcut-ai]

Triage Summary 📝

• Component: testing (confidence: 0.65)
• Category: test (confidence: 0.80)
• Priority: p2 (confidence: 0.70)

Because the component and priority confidence are below 0.75, the needs-human-triage label has been applied so a maintainer can confirm.

Missing information ❓

Please help us proceed by providing:

1. The specific user journeys or database scenarios to automate.
2. Supported browsers/devices and any required seeded data or credentials.
3. Clarification on whether these tests need to run in CI, and how strict the "run all tests twice" requirement is (local vs CI, reporting expectations).
4. How closely we should mirror the falkordb-browser e2e architecture (helpers, CI wiring).

Once we have this information we can refine scope and prioritize implementation. Thank you!

Log: automated triage applied labels category/tests, needs-info, needs-human-triage.