Fix client trackinginfo crash when tracking off by default

[yangbodong22011]

After #1405, client trackinginfo will crash when tracking is off

/lib64/libpthread.so.0(+0xf630)[0x7fab74931630]
./src/valkey-server *:6379(clientTrackingInfoCommand+0x12b)[0x57f8db]
./src/valkey-server *:6379(call+0x5ba)[0x5a791a]
./src/valkey-server *:6379(processCommand+0x968)[0x5a8938]
./src/valkey-server *:6379(processInputBuffer+0x18d)[0x58381d]
./src/valkey-server *:6379(readQueryFromClient+0x59)[0x585ea9]
./src/valkey-server *:6379[0x46fa4d]
./src/valkey-server *:6379(aeMain+0x89)[0x5bf3e9]
./src/valkey-server *:6379(main+0x4e1)[0x455821]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fab74576555]
./src/valkey-server *:6379[0x4564f2]

The reason is that we did not init pubsub_data by default, we only
init it when tracking on.

Fixes #1683.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.05%. Comparing base (fc55142) to head (8c2737b).
Report is 6 commits behind head on unstable.

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable    #1684      +/-   ##
============================================
+ Coverage     71.02%   71.05%   +0.03%     
============================================
  Files           121      121              
  Lines         65254    65313      +59     
============================================
+ Hits          46344    46410      +66     
+ Misses        18910    18903       -7     

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

... and 14 files with indirect coverage changes

[enjoy-binbin]

@uriyage please take a look

[zuiderkwast]

Checking the flag seems to be not enough. We got this in the CI job:

Test case CLIENT TRACKINGINFO provides reasonable results when tracking on.

7635:M 07 Feb 2025 14:56:21.674 # === ASSERTION FAILED ===
7635:M 07 Feb 2025 14:56:21.674 # ==> networking.c:4104 'c->pubsub_data && c->pubsub_data->client_tracking_prefixes' is not true

[zuiderkwast]

@yangbodong22011 Can you fix the DCO issue?

See the Details link next to the failing DCO CI job. There's some instructions about how to fix it. (git rebase HEAD~3 --signoff and force-push.)

[yangbodong22011]

@yangbodong22011 Can you fix the DCO issue?

See the Details link next to the failing DCO CI job. There's some instructions about how to fix it. (git rebase HEAD~3 --signoff and force-push.)

Sorry for late, done.