Latency reset update and latency histogram

[watersRand]

feat(client): implement LATENCY RESET UPDATE and LATENCY HISTOGRAM commands

Adds two new latency-related commands to the node-redis client:

• LATENCY RESET: Clears latency samples for specific events or all events.
• LATENCY HISTOGRAM: Provides detailed latency distribution information for Redis events.

Description

This Pull Request introduces two new Redis commands to the node-redis client, enhancing its capabilities for Redis performance monitoring and analysis.

1. LATENCY RESET Command:

• Purpose: Allows users to programmatically reset Redis latency statistics, enabling cleaner monitoring cycles or targeted troubleshooting.
• Implementation Details:
  • Implemented parseCommand to correctly format the LATENCY RESET command with optional event arguments (e.g., LATENCY RESET command, LATENCY RESET fork).
  • Implemented transformReply to handle the integer reply from Redis, representing the number of events reset.
  • Comprehensive unit tests (LATENCY_RESET.spec.ts) are included for argument transformation and an integration test verifies end-to-end functionality against a live Redis server.
• Redis Documentation Reference: https://redis.io/commands/latency-reset/

2. LATENCY HISTOGRAM Command:

• Purpose: Provides granular insights into command execution times and other event latencies by exposing Redis's internal latency histograms.
• Implementation Details:
  • Implemented parseCommand to correctly format the LATENCY HISTOGRAM command, supporting the optional BUCKETS argument.
  • Implemented transformReply to parse the nested array reply from Redis into a user-friendly array of LatencyHistogramBucket objects, correctly calculating max values and handling '+inf'.
  • Comprehensive unit tests (LATENCY_HISTOGRAM.spec.ts) are included to ensure parseCommand correctly transforms arguments (with and without BUCKETS), and transformReply accurately parses various reply formats (typical, empty, single bucket, and malformed).
  • An integration test is provided to verify the end-to-end functionality of client.latencyHistogram against a live Redis server, including generating latency events and asserting the histogram's structure.
• Redis Documentation Reference: https://redis.io/commands/latency-histogram/

General Changes for Both Commands:

• Updated packages/client/lib/commands/index.ts to expose both LATENCY RESET and LATENCY HISTOGRAM commands with their respective camelCase aliases (latencyReset, latencyHistogram).

Testing Environment Note (Important!):
During local development and testing on a GCP Compute Engine VM, I encountered persistent timeouts related to Docker container startup and client connection. To ensure the tests could run to completion, I temporarily modified the internal timeout within node_modules/@redis/test-utils/dist/lib/index.js (specifically, increasing this.timeout in the testWithClient hook from 30s to 5min). This modification was purely for my local testing environment and is not part of this core contribution. It should not be merged into the main codebase. The tests were successfully run against redislabs/client-libs-test:8.2-rc1.

[nkaradzhov]

Can you please remove package-lock.json
Can you also fix the formatting

[nkaradzhov]

Can you add jsdoc here

[nkaradzhov]

can you add jsdoc here