feat(script): Support script flags of Eval script and Function

[PokIsemaine]

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.

[mapleFU]

Just ping me if ready for code review

[PragmaTwice]

I think inside the lua vm we can have such global variables:

f_<sha>_flags  ->  <flags (encoded to integer)>
__redis_registered_flags_<func name>  ->  <flags (encoded to integer)>

and we can construct ctx quickly when the lua function is called.

[PokIsemaine]

The converting integer part uses the lua_tointegerx API, which actually belongs to lua 5.2. luaJIT is compatible with lua 5.1 and also extends this API, but lua 5.1 itself does not support it.
I use this API because I want to detect the case where the conversion to integer fails, I don't use lua_tointeger because on failure it returns 0, which is indistinguishable from a true 0.
Two possible solutions:

1. Upgrade lua to 5.2
2. Just use lua_tointeger and the conversion is successful by default. The flags stored to lua here are controlled, generated by kvrocks and illegal flags should be detected during parsing. I think we can ignore the detection during conversion.

What do you think, or is there a better solution? @PragmaTwice

[PragmaTwice]

I think maybe we can just use lua_isinteger to check before calling lua_tointeger?

[PokIsemaine]

I think maybe we can just use lua_isinteger to check before calling lua_tointeger?

This API seems to be supported by lua 5.3

[git-hulk]

LGTM, this PR is in good shape.

[PragmaTwice]

LGMT except that I'm not so familiar with the impl of Cluster::CanExecByMySelf.

cc @mapleFU @git-hulk could you check it when you have time?

[git-hulk]

LGMT except that I'm not so familiar with the impl of Cluster::CanExecByMySelf.

cc @mapleFU @git-hulk could you check it when you have time?

Sure, I have checked and looks good from my side.

[git-hulk]

@mapleFU To see if you have further comments? or we can merge this PR to avoid pending too long.

[sonarqubecloud]

Quality Gate passed

Issues
12 New issues
0 Accepted issues

Measures
0 Security Hotspots
73.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud