feat(sdk): stop bypassing UserPresence:* methods — let them hit DDPSDK

The original bypass for UserPresence:setDefaultStatus / online / away was
a performance guard: REST round-trips were expensive for the frequent
heartbeat-style calls, so they stayed on the Meteor DDP WS. With the
DDPSDK WebSocket now carrying the rest of the RPC traffic, that
rationale no longer applies — they can ride the same socket as every
other sdk.call.

logout and setUserStatus stay on the bypass list for now. logout mutates
per-connection auth state that the Accounts.onLogout chain relies on,
and setUserStatus currently feeds the legacy Meteor user stream.

Author: ggazzo

apps/meteor/client/meteor/overrides/ddpOverREST.ts

@@ -16,7 +16,12 @@ const shouldBypass = ({ msg, method, params }: Meteor.IDDPMessage): boolean => {
 		return true;
 	}
 
-	if (method.startsWith('UserPresence:') || bypassMethods.includes(method)) {
+	// `logout` mutates per-connection auth state on Meteor's side; keeping it on
+	// Meteor.connection ensures the subsequent Accounts.onLogout chain (userId
+	// cleanup, ServerContext status flip, etc.) fires as before.
+	// `setUserStatus` toggles `_updatedAt` and presence fields that the Meteor
+	// user stream is still expected to drive while it remains the auth anchor.
+	if (bypassMethods.includes(method)) {
 		return true;
 	}