v1.6.71 — Socket settings from the console; live and test-mode API caches kept apart; driver-assigned events on driver channels

Added

Socket settings from the console. System administrators manage realtime channel authentication without touching the environment: GET/POST int/v1/settings/socket read and save the switch, the mode (off, log, enforce), the token TTL, the allowed origins and the publisher origin. Each value falls back to the environment when unset, so nothing changes until an administrator saves something. A signed GET int/v1/socket/config lets the socket server (fleetbase/fleetbase v0.7.70) poll the effective config and apply it at runtime, no restart. SOCKETCLUSTER_AUTH_KEY stays in the environment and is never stored or returned; turning the switch on without a key is refused. Every save is written to the activity log. (#314)
Category parent_uuid on internal responses. The internal Category resource now includes parent_uuid, so a console can build a category tree from a flat list (Storefront's nested product categories). (#316)

A controller's filter is used for every query it serves. Find::httpFilterForModel() cached its answer per model class for the life of the process, ignoring the filter a controller sets on its model ($filter) and whether the request was internal. Under Octane, the first controller to list a model decided the filter for every other: Fleet-Ops' order filter was applied to Storefront's order lists, so a network's orders page listed every order in the company. The cache is now keyed by the model's own filter, and a filter found by convention is picked per request audience. Find::httpRequestForModel() is keyed by the model's own request class too. (#315)
Live and test-mode data no longer share API cache entries. List, model and relationship cache keys now carry the database connection ({api_query}:mysql:… / {api_query}:sandbox:…). Before, a console request in test mode could be served the cached live response for the same query (and the reverse), because console sessions carry no API credential to tell the two apart. (#312)
Driver-assigned lifecycle events reach driver.{public_id} and driver.{uuid}. Order events for records with an assigned driver were only published on driverAssigned.*, which clients following the {type}.{id} convention never subscribe to. driverAssigned.* is still published and is now deprecated. (#311)

Socket settings: nothing changes until an administrator saves one; the environment values stay the defaults. A socket server older than fleetbase/fleetbase v0.7.70 keeps reading its own environment.
Otherwise none. Existing cache entries keep their old keys and expire within their TTL (5 minutes for lists, 1 hour for models); deploy.sh already runs php artisan cache:clear.

fix(events): publish driver-assigned records on driver.{id} by @roncodes in #311
fix: isolate API model cache keys between live and sandbox by @roncodes in #312
feat(socket): admin socket settings (switch, mode, token TTL, origins) with signed config for the socket server by @roncodes in #314
fix(find): key the filter and request caches by the controller's own class by @roncodes in #315
feat(categories): include parent_uuid in internal category responses by @roncodes in #316
release: v1.6.71 by @roncodes in #313

Full Changelog: v1.6.70...v1.6.71