feat(frontend-main): add e2e testing with Keplr integration

[luciorubeens]

• Set up Playwright e2e testing structure
• Add Keplr wallet fixtures and page objects
• Implement automated extension setup and wallet import
• Add basic test specs for authenticated and public flows

[netlify]

✅ Deploy Preview for dither-staging ready!

Name	Link
🔨 Latest commit	c731dd3
🔍 Latest deploy log	https://app.netlify.com/projects/dither-staging/deploys/691d933b095bcd000864cc51
😎 Deploy Preview	https://deploy-preview-478--dither-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mazzy89]

The tests setup uses testnet API as backend. Isn't risky to make mutation calls to the testnet API backend? In other words are we ensuring to have tests idempotent so they can run several times without changing the state of the testnet API backend?

[luciorubeens]

@mazzy89 For now, these e2e tests are designed for ui and user flow validation only, with no mutation calls. The test wallet has no funds, which ensures that no on-chain state changes can occur. There is also no endpoint in the api that we can call directly, everything goes through the indexer.

Ideally, we could spin up a fresh api and chain in the workflow. I believe this is possible using containers, right? But that’s something for another PR.

[mazzy89]

Completely agree w/ you we should spin up fresh instance of api for e2e tests. Let's create an issue about that.