Add new SCRIPT STATS subcommand

[artikell]

An inspiration is needed to query the execution of the current script. Solve this problem https://github.com/orgs/valkey-io/discussions/1404

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.89%. Comparing base (4f61034) to head (b103f0f).
Report is 26 commits behind head on unstable.

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable    #1418      +/-   ##
============================================
+ Coverage     70.85%   70.89%   +0.03%     
============================================
  Files           118      118              
  Lines         63591    63627      +36     
============================================
+ Hits          45058    45108      +50     
+ Misses        18533    18519      -14     

Files with missing lines	Coverage Δ
src/commands.def	100.00% <ø> (ø)
src/eval.c	57.69% <100.00%> (+0.67%)	⬆️

... and 12 files with indirect coverage changes

[madolson]

Is the thought we will have more stats in the future? I'm wondering if we should just have a command just for the running script, instead of something generic like stats.

[artikell]

To be honest, this part is a reference to FUNCTION STATS.
Currently, there is really only one return value., but as a stat method, it is best to reserve the ability for subsequent extensions.
Alternatively, we can consider adding some Lua-related context, such as Lua execution time/ Lua use Memory, to help users locate problems.

[madolson]

Why the f$% did the Redis folks do this. I swear they barely thought through functions and then dumped it on the community.