feat(platform): add X (Twitter) connector support in desktop app

[nxved]

Summary

Adds desktop support for the X Playwright connector so it is recognized in platform mapping and bundled with desktop resources.

Changes

• Update platform registry mapping for X:
  • /Users/nextstep/Documents/data-connect/desktop-app/src/lib/platform/registry.ts
  • maps platformIds to include x-playwright
  • aligns aliases and ingestScope for X connector ingestion
• Bundle X connector files in Tauri resources:
  • /Users/nextstep/Documents/data-connect/desktop-app/src-tauri/tauri.conf.json
  • adds ../connectors/x/**/* -> connectors/x/

Validation

• Desktop app boots with connector resources including connectors/x.
• Manual run path validated with X connector output in DataConnect runtime.

Companion PR

Companion connector PR (data-connectors): vana-com/data-connectors#15

[callumflack]

Hi @nxved, thanks for putting this together.

I’ve gone ahead and pushed a follow-up directly onto your branch so the ambiguity about X/Twitter aliasing is resolved on our side rather than bounced back to you.

The main decision we made was to treat x as the single canonical platform entry. We removed the separate legacy twitter registry entry and kept twitter only as a backward-compat alias to x. In other words: for this product, Twitter is legacy naming and X is the canonical source.

Also added a small test around platform resolution so that behavior is protected.

The remaining dependency is external: this desktop-side branch still depends on the feat/x-connector PR in data-connectors before final merge.

If you disagree with the X/Twitter decision we can talk it through, but we wanted to be explicit and decisive about the product direction here.