Remove static to avoid compiler warning

[madolson]

We have some compilation error which to me looks like a false positive, https://github.com/valkey-io/valkey/actions/runs/10127360669/job/28005048552. It seems very similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104165, which is apparently related to miscalculation of static function sizes.

Removing the static just to get the build working, given that most of the codebase still doesn't use static consistently, was thinking about just leaving this way.

NOTE: This would not have been caught with the extra-test label, since we don't run the extra address sanitizers as part of the extra tests, so maybe we should give that this was missed.

Testing

See https://github.com/madolson/valkey/actions/runs/10133662275/job/28019055701 for valida

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.25%. Comparing base (e32518d) to head (744147b).

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable     #836      +/-   ##
============================================
+ Coverage     70.20%   70.25%   +0.04%     
============================================
  Files           112      112              
  Lines         61462    61462              
============================================
+ Hits          43152    43180      +28     
+ Misses        18310    18282      -28     

Files	Coverage Δ
src/cluster_legacy.c	85.42% <100.00%> (-0.04%)	⬇️

... and 11 files with indirect coverage changes

[roshkhatri]

Agreed, we should add a mechanism to catch these errors before merging. Or add these tests to be run with the extra-tests label?