feat(chat): real-time chat with the driver on an order

[roncodes]

Summary

This implements real-time chat with the driver from the redesign prototype. It's stacked on feat/notifications and uses the order chat API from fleetbase/storefront#117, with socket authorization from fleetbase/core-api#290.

Order chat (order.chat, route OrderChat)

• Header: back to tracking, the driver's avatar (or initials) with a presence dot, name, "Your driver · #order · online", and a call button when the driver's phone is known.
• Messages:
  • an intro notice;
  • bubbles (yours on the right in the brand colour, the driver's on the left) with photos, times and "Read" on your messages;
  • older messages load as you scroll up (before cursor).
• Composer: quick replies ("Coming down now", "Please leave it at the door", …), photo sending (up to four), and text up to 2000 characters.
• Optimistic sending: a message shows straight away as "Sending…". It's replaced by the server copy when confirmed, or offers "Not sent · Tap to retry".
• Live updates: the screen subscribes to the chat's socket channel. Any chat_* event re-reads the latest messages, which keeps it independent of the socket payload shape. The driver's messages are marked read when they arrive or when the chat opens. A "Reconnecting…" banner shows while the socket is down. Sending still works then, because it goes over HTTP.
• States:
  • No driver yet (409 driver_not_assigned), with retry.
  • Load error.
  • Closed once the order is finished: read-only, with a note to contact the store. A send refused with 423 chat_closed closes the composer.
  • Signed out.

Tracking

• The driver card gets a Message button with the unread count.
• After the order is finished: "Chat with your driver closed when the order was finished. View messages".
• Driver-message notifications (inbox and push) now open the chat.

Shared code

• src/commerce/order-chat.ts: parsing, merging (server copies replace local ones; unsent messages stay last), and the chat endpoints.
• src/commerce/http.ts: requests that keep the status and reason of refusals. The SDK adapter only keeps errors[0].
• useChatRequest: chat calls with the customer token.

Backend fix in #117

The chat payload advertised chat_channel.{uuid}. That channel is authorized, but core broadcasts chat events on chat.{id}, so live messages would never have arrived. #117 now returns chat.{public_id}. Its suite passes (612 tests) with every changed line covered.

Not included

Typing indicators: there are no typing events to listen to.

Testing

• Unit tests: __tests__/commerce/order-chat.test.ts, covering the chat module and apiRequest.
• yarn jest: 188 tests pass. yarn typecheck:strict is clean. yarn lint:strict has 0 errors.
• Not tested yet:
  • a live chat: it needs #117 and core-api#290 deployed, a signed-in customer and an assigned driver;
  • the chat screen's rendering: the local API has no customer account, so the preview never got past the signed-out state.