Upgrade @ably/chat to v1.3.1 and remove useBinaryProtocol workaround

The new Chat SDK version fixes the MsgPack/binary protocol issue with
realtime.request() REST calls, so the getClientOptions override that
set useBinaryProtocol=false is no longer needed.

Author: umair-ably

README.md

@@ -2038,6 +2038,8 @@ EXAMPLES
 
   $ ably channels presence update my-channel --data '{"status":"busy"}' --json
 
+  $ ably channels presence update my-channel --data '{"status":"busy"}' --pretty-json
+
   $ ably channels presence update my-channel --data '{"status":"online"}' --duration 60
 ```
 

package.json

@@ -110,7 +110,7 @@
     }
   },
   "dependencies": {
-    "@ably/chat": "^1.0.0",
+    "@ably/chat": "^1.3.1",
     "@ably/spaces": "^0.4.0",
     "@inquirer/prompts": "^5.1.3",
     "@oclif/core": "^4.2.10",

pnpm-lock.yaml

@@ -1,4 +1,3 @@
-import type * as Ably from "ably";
 import { ChatClient, Room, RoomStatus } from "@ably/chat";
 
 import { AblyBaseCommand } from "./base-command.js";
@@ -17,17 +16,6 @@ export abstract class ChatBaseCommand extends AblyBaseCommand {
   private _chatClient: ChatClient | null = null;
   private _cleanupTimeout: NodeJS.Timeout | undefined;
 
-  /**
-   * Override getClientOptions to disable binary protocol for Chat commands.
-   * The Chat API uses realtime.request() for REST calls, and binary (MsgPack)
-   * encoding is not supported by the Chat API endpoints.
-   */
-  protected override getClientOptions(flags: BaseFlags): Ably.ClientOptions {
-    const options = super.getClientOptions(flags);
-    options.useBinaryProtocol = false;
-    return options;
-  }
-
   /**
    * finally disposes of the chat client, if there is one, which includes cleaning up any subscriptions.
    *