Node.js: Phase 2 client-side caching - serverAssisted field and clientTrackingInfo

[affonsov]

Summary

Adds serverAssisted field to Node.js ClientSideCache config and clientTrackingInfo() diagnostic command.

Issue link

This Pull Request is linked to issue: Implement client-side caching Phase 2: server-assisted invalidation via CLIENT TRACKING
Closes #5961

Features / Behaviour Changes

• serverAssisted?: boolean in ClientSideCacheConfig interface and ClientSideCache class (default false)
• clientTrackingInfo() on BaseClient - available on both GlideClient and GlideClusterClient
• clientTrackingInfo(options?: RouteOption) cluster override on GlideClusterClient for routing to specific nodes
• clientTrackingInfo() in BaseBatch

Implementation

• ClientSideCache.ts: serverAssisted field added to config interface and class; serialized to protobuf
• BaseClient.ts: clientTrackingInfo() - routes to a single node, consistent with CLIENT INFO behavior
• GlideClusterClient.ts: cluster override with optional RouteOption - use AllNodes to get tracking info from all cluster connections
• Batch.ts: batch method

Limitations

• serverAssisted: true requires RESP3 protocol (enforced by glide-core)
• In cluster mode, the no-arg variant routes to a single random node; use RouteOption to query all nodes

Testing

• Unit test verifying serverAssisted field defaults and construction
• Integration tests are in the glide-core PR Core: Phase 2 client-side caching - server-assisted invalidation via CLIENT TRACKING #5962

Checklist

• This Pull Request is related to one issue.
• Commit message has a detailed description of what changed and why.
• Tests are added or updated.
• CHANGELOG.md and documentation files are updated.
• Linters have been run and Prettier has been run.
• Destination branch is correct - main or release
• Create merge commit if merging release branch into main, squash otherwise.