feat(realtime): use phoenix's js lib inside realtime-js

[GuzekAlan]

🔍 Description

Make realtime-js use phoenix js library to handle most of the logic.

What changed?

Most of the code now uses adapters to use phoenix API

Why was this change needed?

It shifts the responsibility for creating, handling, and cleaning connections and channels to phoenix js library. Only Supabase related logic for auth, and bindings filtering/formatting along exposing proper API is contained in the realtime-js

🔄 Breaking changes

• there is no way to subscribe after unsusbcirbe - it wasn't working properly in the original implementation
• WebSocket implementation errors will be thrown in constructor (instead of connect) -since getWebsocketConstructor is used in RealtimeClient.constructor
• calling on with presence after subscribe will result in error - due to no resubscribe funcitonality
• no teardown on RealtimeClient.disconnect - now channels are maintaining it's information and when socket is reconnected they keep working (this is the way phoenix does it)
• callbacks (used in on method) can take joinRef as a 3rd parameter
• fields which are used internally are mainly read-only

📋 Checklist

• I have read the Contributing Guidelines
• My PR title follows the conventional commit format: <type>(<scope>): <description>
• I have run npx nx format to ensure consistent code formatting
• I have added tests for new functionality (if applicable)
• I have updated documentation (if applicable)

📝 Additional notes

In this PR some tests are removed because they are moved to https://github.com/supabase/phoenix

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/core/realtime-js/src/RealtimeChannel.ts`:
- Around line 352-353: The call to this.unsubscribe() in the error path is not
awaited so any rejection will be swallowed; change it to await
this.unsubscribe() inside the async handler (or append .catch(...) to log the
failure) before setting this.state = CHANNEL_STATES.errored so unsubscribe
errors are surfaced or at least logged; update the method that contains
this.unsubscribe() (the RealtimeChannel unsubscribe/error handling branch) to
either await the promise or handle rejection with a logger (e.g.,
this.unsubscribe().catch(err => this.logger.error(...))).

---

Duplicate comments:
In `@packages/core/realtime-js/src/RealtimeChannel.ts`:
- Line 175: The public field bindings on class RealtimeChannel (bindings:
Record<string, Binding[]>) is undocumented; add a concise JSDoc comment above
the bindings declaration describing its purpose, shape, and intended visibility
(e.g., "map of event names to listener bindings") or, if this is not part of the
public API, mark it as `@internal` in the JSDoc and explain why consumers should
not use it; ensure the comment mentions the Binding type and any invariants
(e.g., ownership/lifecycle) so readers understand how to interact with or avoid
the field.

In `@packages/core/realtime-js/src/RealtimeClient.ts`:
- Around line 116-181: The proxy getters on RealtimeClient (endPoint, timeout,
transport, heartbeatCallback, heartbeatIntervalMs, heartbeatTimer,
pendingHeartbeatRef, reconnectTimer, vsn, encode, decode, reconnectAfterMs,
sendBuffer, stateChangeCallbacks) are missing JSDoc visibility; if these are not
part of the public API mark each getter with `@internal` JSDoc (or add brief
public JSDoc if they should be public) so the intent is clear and the TypeDoc
output is correct; update the comment block above each getter (or a shared block
above the group) to include `@internal` and a one-line description, and ensure the
stateChangeCallbacks return-type annotation remains accurate.

In `@packages/core/realtime-js/test/RealtimeClient.resilience.test.ts`:
- Around line 6-14: The resilience tests manipulate reconnection and heartbeat
timing but currently run with real timers, which can cause flakiness; update the
test setup to enable fake timers in the beforeEach where testClient is
initialized (call the test runner's fake timer API, e.g., vi.useFakeTimers or
jest.useFakeTimers) and restore real timers in afterEach alongside
testClient.cleanup (e.g., vi.useRealTimers or jest.useRealTimers), and adjust
any timing-based assertions in tests to use the timer-control helpers
(advanceTimersByTime/advanceTimersToNextTimer) to drive reconnection/heartbeat
behavior deterministically for functions/setupRealtimeTest and the surrounding
beforeEach/afterEach.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/core/realtime-js/src/phoenix/presenceAdapter.ts`:
- Around line 17-37: The onJoin/onLeave handlers emit raw Phoenix metas
(newPresence['metas'] / leftPresence['metas']) while transformState normalizes
to presence_ref, causing inconsistent payload shapes; update the handlers in
presence.onJoin and presence.onLeave to map/normalize each meta to the same
shape used by transformState (replace phx_ref with presence_ref and preserve
other fields) before passing currentPresences/newPresences/leftPresences to
channel.getChannel().trigger so join/leave events match transformState output
(use parseCurrentPresences and the same normalization routine applied in
transformState).

[coderabbitai]

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@packages/core/realtime-js/src/phoenix/presenceAdapter.ts`:
- Around line 96-116: transformState currently mutates Phoenix's presence metas
by deleting phx_ref and phx_ref_prev, which corrupts Phoenix internal state used
by onLeavePayload (via parseCurrentPresences). Change transformState to return
new objects without mutation (e.g. for each meta create a new object: extract
phx_ref and phx_ref_prev and return { ...rest, presence_ref: phx_ref }) so phx_*
fields are not deleted from the original metas; ensure parseCurrentPresences
continues to call transformState and does not pass through live references.