feat: add Playwright browser compatibility tests (#348)

[JafetCHVDev]

Summary

Adds browser compatibility testing infrastructure using Playwright, running across Chromium, Firefox, and WebKit.

Changes

• Playwright test suite — 3 browser specs (Chromium/Firefox/WebKit) validating SDK ESM bundle loads and key APIs
• Test harness — \ ests/browser/harness.html\ with inline test runner for SDK exports, StreamBuilder, utility functions, and error classes
• Stellar SDK shim — \ ests/browser/stellar-shim.js\ mapped via importmap to avoid CDN dependency for @stellar/stellar-sdk\
• Static file server — \ ests/browser/server.cjs\ serving the repo root for Playwright webServer config
• CI update — .github/workflows/ci.yml\ updated to install Playwright browsers and run browser tests

Testing

All 9 tests pass (3 browsers × 1 test each):

\
9 passed (6.9s)
\\

Closes #348

[drips-wave]

@JafetCHVDev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Jaydbrown]

Good idea, but a few things need fixing before this is mergeable:

1. .gitignore is corrupted — it's a mixed-encoding file now (git diff even shows it as "Binary files ... differ"). The tail of the file switches from plain ASCII to what looks like UTF-16LE for the test-results/ entry (each character followed by a null byte). This needs to be a clean, plain-text append of whatever new entries this PR needs (presumably test-results/, Playwright's report output dir), not a re-encoded file.

2. tests/browser/serve.ts is dead code — it's a near-duplicate of tests/browser/server.cjs (same static file server, same MIME map, same path-traversal guard), but nothing imports or invokes it; playwright.config.ts's webServer.command runs server.cjs, not this. Please delete serve.ts (or delete server.cjs and wire playwright.config.ts to the TS version instead, if that's actually the intended one) — having two implementations of the same thing invites drift.

3. No way to actually run this — there's no test:browser (or similar) script added to package.json, and .github/workflows/ci.yml isn't touched at all. As submitted, this is test infrastructure that nothing will ever invoke automatically; it'll only run if someone remembers the exact npx playwright test --config=tests/browser/playwright.config.ts invocation by hand. Please add an npm script and, ideally, a CI job (even if it only runs on a separate/optional workflow given browser installs are heavier than the unit suite).

4. Minor: the 3 tests in compatibility.spec.ts ("...in Chromium" / "...in Firefox" / "...in WebKit") are byte-for-byte identical — the actual per-engine matrix already comes from playwright.config.ts's projects array (each project runs every spec once). Consider collapsing these into a single test since the browser-name-specific test titles don't correspond to anything different in the test bodies themselves.

The harness/shim approach (import-map-based ESM loading of dist/esm/index.js against a stub SDK dependency) looks reasonable — happy to take another pass once the above is addressed.