Redact protocol error log when hide-user-data-from-log enabled

[YueTang-Vanessa]

In this code logic: https://github.com/valkey-io/valkey/blob/unstable/src/networking.c#L2767-L2773, c->querybuf + c->qb_pos may also include user data.
Update the log message when config hide-user-data-from-log is enabled.

[zuiderkwast]

When exactly is this triggered? Only when the client sends some incorrectly encoded RESP?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.00%. Comparing base (06990c2) to head (1b77cf5).
Report is 4 commits behind head on unstable.

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable    #1889      +/-   ##
============================================
- Coverage     71.00%   71.00%   -0.01%     
============================================
  Files           123      123              
  Lines         65671    65675       +4     
============================================
+ Hits          46631    46632       +1     
- Misses        19040    19043       +3     

Files with missing lines	Coverage Δ
src/networking.c	88.78% <100.00%> (+0.12%)	⬆️

... and 15 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hpatro]

Could you add a test case and assert *redacted* on it ?.

[QuChen88]

Looks good to me

[QuChen88]

@zuiderkwast Basically any sort of protocol parsing error from the primary to the replica can lead to this condition to get triggered and the query buffer containing potential user data/commands would get logged. This can happen for various reasons including data corruption over the wire etc. i.e. we saw this in a couple of our redis clusters in the past.

3524:S 26 Mar 2025 17:49:50.755 # WARNING: Receiving inline protocol from master, master stream corruption? Closing the master connection and discarding the cached master.
3524:S 26 Mar 2025 17:49:50.755 # Protocol error (Master using the inline protocol. Desync?) from client: ... Query buffer during protocol error: '293..$4..hdel..$31.. <key-name>...

The chances of this happening is pretty low, but still non zero.