Consider disabling LUAI_ASSERT in tests for PUC Rio Lua

[ligurio]

Bytecode parser in PUC Rio Lua does not strict and malicious bytecode can trigger assertions enabled by macro LUAI_ASSERT (internal assertions for in-house debugging). These cases are often false positive.
Let's consider disabling LUAI_ASSERT in the following tests: luaL_loadbufferx_test ¹, lua_load_test ² and lua_dump_test ³.

See:

• luaL_loadbufferx_test fuzzer crashes in loadString in lundump.c #132
• lua_dump_test, https://oss-fuzz.com/testcase-detail/5639714608840704
• lua_load_test, https://oss-fuzz.com/testcase-detail/4813531965095936

Footnotes

1. https://github.com/ligurio/lua-c-api-tests/blob/0508724910b252010ae5f6bcaef0e54cf198cf5b/tests/capi/luaL_loadbufferx_test.c ↩

2. https://github.com/ligurio/lua-c-api-tests/blob/0508724910b252010ae5f6bcaef0e54cf198cf5b/tests/capi/lua_load_test.cc ↩

3. https://github.com/ligurio/lua-c-api-tests/blob/0508724910b252010ae5f6bcaef0e54cf198cf5b/tests/capi/lua_dump_test.c ↩