Upgrade to Pusher JS 8.5.0 - Beta release

This release upgrades the bundled Pusher client from 7.0.6 to 8.5.0, adds support for Pusher's v8 features (subscription counts, user authentication, watchlist, cluster switching), and hardens the wrapper against common runtime errors.

⚠️ Breaking changes — read before upgrading

• cluster is now mandatory and must be a valid Pusher cluster id (e.g. mt1, us2, us3, eu, ap1–ap4, sa1). Values like us-east-1 are AWS regions, not Pusher clusters, and will fail. Set it in your Pusher_Options. Default is now mt1.
• Channel/user auth options renamed. Use channelAuthorization: { endpoint, transport } for private/presence channels and userAuthentication: { endpoint, transport } for sign-in. The old flat auth / authEndpoint / authTransport options are deprecated.
• OnMessageReceived argument order is now consistent across all binding paths: (data, event, channel). Previously, messages from channels subscribed at init delivered channel/event in swapped positions — if you compensated for that, remove the workaround.
• Message payloads are always delivered as text (JSON). All event-binding paths now serialize object payloads to a JSON string, so your OnMessageReceived handler can consistently JSONDeserialize. 

New client actions

• Subscription Count: EnableSubscriptionCount, DisableSubscriptionCount, GetSubscriptionCount + OnSubscriptionCount event
• User: Signin, BindUser, BindUserGlobal, UnbindUser, UnbindUserGlobal + OnUserEvent event
• Watchlist: EnableWatchlist, DisableWatchlist + OnWatchlistEvent event
• Connection: SwitchCluster — change cluster/app without losing subscriptions

Reliability fixes

• No longer crashes when a channel entry is missing a name or when acting on a channel before subscribing — these now log and no-op instead.
• Initialization is idempotent: re-rendering the block (OnParametersChanged) no longer double-subscribes or duplicates event handlers.
• A throwing client-action handler can no longer break the Pusher connection.
• Added Destroy cleanup that disconnects, unbinds, and releases the instance.

Notes

• The three new callback events (OnSubscriptionCount, OnUserEvent, OnWatchlistEvent) are optional — existing screens upgrade without wiring them.
• User authentication and watchlist require server-side endpoints and the corresponding features enabled on your Pusher app.