Fix parsing for object store commands with wrong number of arguments

[lmaas]

This PR addresses a critical bug related to object store commands, where command invocations with incorrect numbers of arguments can corrupt the command stream by prematurely exiting the parsing loop without fully consuming the RESP command.

Bug Description

Steps to Reproduce

redis> HSET x y "Hello"
(integer) 1
redis> HLEN x y # <- Incorrect input
(integer) 0
redis> HGET x y
(error) ERR unknown command

Expected Result

redis> HGET x y
"Hello"

Actual Result

Due to the parsing stream assuming that “y” is the next command name, the subsequent command is incorrectly flagged as unknown.

Changes

To fix this issue, the following changes have been made:

• Replaced WriteErrorTokenNumberInCommand() with a new function called AbortWithWrongNumberOfArguments(). This new function ensures that any remaining arguments left in the input stream are properly drained before returning the error related to incorrect #arguments.
• Corrected the maximum number of arguments for the following commands: HLEN, HEXISTS, HINCRBY, HINCRBYFLOAT, SCARD, and ZCARD.