The remote console is enabled for debugging purposes. It can be helpful when Tarantool is stuck and one need an access to console to gather an additional information about Tarantool (like `fiber.info` output or anything else). NO_CHANGELOG=testing NO_DOC=testing

`vy_page_stmt()` may fail (return NULL) if: - the statement is corrupted; - memory allocation for the statement fails; - the statement size exceeds `box.cfg.vinyl_max_tuple_size`. If this happens `vy_page_find_key()` won't return an error. Instead, it'll either point the caller to a wrong statement or claim that there's no statement matching the key in this page. This may result in invalid index selection results and, later on, a crash caused by inconsistencies in the tuple cache. The issue was introduced by commit ac8ce0233a00 ("vinyl: factor out function to lookup key in page"). All of the three cases are actually very unlikely to happen in production: - If a statement stored in a run file is corrupted, we'll probably fail to load the whole page due to failed checksums and never even get to `vy_page_stmt()`. - Statements are allocated with `malloc()`, which doesn't normally fail (instead the whole process would be terminated by OOM) . - Users don't tend to lower the tuple size limit after restart. Still, let's fix the issue by implementing proper error handling for `vy_page_find_key()`. Closes #10512 NO_DOC=bug fix

NO_TEST=the new function is called in the test-covered function @TarantoolBot document Title: Document `box_slab_info` C API function Since: Tarantool 3.3.0 Added the new C function `box_slab_info` that returns information about the memory state depending on the passed argument `box_slab_info_type`. The same information is available in Lua via `box.slab.info()`.

Part-of #10211 NO_TEST=internal NO_CHANGELOG=internal NO_DOC=internal

Part-of #10211 NO_TEST=internal NO_CHANGELOG=internal NO_DOC=internal