ci: enable E2E tests in CI

[xilosada]

Summary

Uncomments the E2E test job in CI. Requires merod >= 0.10.1-rc.14 (Docker image ghcr.io/calimero-network/merod:prerelease) which includes the X-Auth-Error: token_expired header fix.

Do not merge until rc14 is released.

What the E2E job does

1. Pulls merod from Docker image
2. Inits + starts a local node with embedded auth
3. Installs the kv-store test app bundle (committed fixture)
4. Runs 29 E2E tests: auth, applications, contexts, RPC, SSE, token management

Test coverage

• Authentication (login, bad credentials, providers, health)
• Applications (list, get, package version)
• Contexts (create, list, get, identities, identities-owned)
• JSON-RPC (read, write, remove, error handling)
• SSE (connect, subscribe, event on mutation)
• Auth helpers (parseAuthCallback, buildAuthLoginUrl)
• Token management (get, set, clear)

Made with Cursor

---

Note

Medium Risk
Adds a new CI job that downloads and runs an external merod binary and executes full E2E tests, which increases CI flakiness risk (network/download/boot timing) and can fail due to upstream release changes.

Overview
Enables a new E2E Tests GitHub Actions job that runs after build and executes Vitest E2E coverage against a locally started merod node.

The workflow now downloads the latest merod Linux tarball from calimero-network/core GitHub Releases, initializes and starts a node, installs the tests/e2e/assets/kv-store.mpk fixture app via the admin API, runs tests/e2e/full-api.test.ts, and always stops the node afterward.

^{Written by Cursor Bugbot for commit fd70af4. This will update automatically on new commits. Configure here.}