fix: #1884, #2133
a part of: #2414

This PR is designed to support three script flags within Eval Script and Function: no-writes, no-cluster, and allow-cross-slot-keys.

Implementation Details
Focus on ScriptRunCtx. I use it to pass context between Lua and C++. Before executing the Lua script, SaveOnRegistry stores the parsed flags in REGISTRY_SCRIPT_RUN_CTX_NAME. During the execution of the Lua script, GetFromRegistry retrieves the flags of the currently executing script. After the script execution ends, it should be set to nil.

For APIs like EVAL, SCRIPT LOAD, and FUNCTION LOAD, the flags parsed from the Eval Script will be stored in Lua's global variable f_<sha>_flags_. The flags parsed by FUNCTION register_function() will be stored in the Lua global variable _registered_flags_<funcname>.

Testing

• Distinguish between the default values with and without #! in the EVAL Script.
• Function’s name= and EVAL Script’s flags= which will not appear simultaneously.
• FUNCTION requires #!lua and name=.
• Even with allow-cross-slot-keys, pre-defined Keys are still prohibited from crossing Slots.
  Different slots on different nodes are still prohibited from crossing Slots. However, slots on the same node are allowed to cross slots when this flag is enabled (generally not recommended).
• The read_only of EVAL_RO, EVALSHA_RO, and FCALL_RO will be added to the script flags, and even if the no-writes flag is not set, checks will still be performed.

Note
Since I am not very familiar with Lua, the rationality and safety of related operations need to be reviewed.