Go: Phase 2 client-side caching - ServerAssisted field and ClientTrackingInfo

[affonsov]

Summary

Adds ServerAssisted field to Go 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 bool field + WithServerAssisted() fluent builder in ClientSideCache
• ClientTrackingInfo() on baseClient - available on both Client and ClusterClient
• ClientTrackingInfoWithOptions() cluster override on ClusterClient for routing to specific nodes
• ClientTrackingInfo() in BaseBatch

Implementation

• config/ClientSideCache.go: ServerAssisted field, WithServerAssisted() builder, serialized in toProtobuf()
• base_client.go: ClientTrackingInfo() - routes to a single node, consistent with CLIENT INFO behavior
• glide_cluster_client.go: ClientTrackingInfoWithOptions() with RouteOptions - use AllNodes to get tracking info from all cluster connections
• response_handlers.go: handleMapOfStringAnyMapResponse for multi-node cluster response

Limitations

• ServerAssisted: true requires RESP3 protocol (enforced by glide-core)
• In cluster mode, the no-arg variant routes to a single random node; use RouteOptions 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.