Fix Server Crash in LCS Command

See https://gist.github.com/antirez/3591c5096bc79cad8b5a992e08304f48

The `LRANK` command returns the index (position) of a given element
within a list. Using the `direction` argument it is possible to specify
going from head to tail (acending, 1) or from tail to head (decending,
-1). Only the first found index is returend. The complexity is O(N).

When using lists as a queue it can be of interest at what position a
given element is, for instance to monitor a job processing through a
work queue. This came up within the Python `rq` project which is based
on Redis[0].

[0]: https://github.com/rq/rq/issues/1197Signed-off-by: NPaul Spooren <mail@aparcar.org>

return the correct proto version

Don't queue commands in an already aborted MULTI state

Avoid rejecting WATCH / UNWATCH, like MULTI/EXEC/DISCARD

AOF: append origin SET if no expire option

fix disconnectSlaves, to try to free each slave.

donot free protected client in freeClientsInAsyncFreeQueue()

the recent change in that loop (iteration rather than waiting for it to
be empty) was intended to avoid an endless loop in case some slave would
refuse to be freed.

but the lookup of the first client remained, which would have caused it
to try the first one again and again instead of moving on.

Much like MULTI/EXEC/DISCARD, the WATCH and UNWATCH are not actually
operating on the database or server state, but instead operate on the
client state. the client may send them all in one long pipeline and check
all the responses only at the end, so failing them may lead to a
mismatch between the client state on the server and the one on the
client end, and execute the wrong commands (ones that were meant to be
discarded)

the watched keys are not actually stored in the client struct, but they
are in fact part of the client state. for instance, they're not cleared
or moved in SWAPDB or FLUSHDB.

HELLO should return the current proto version, while the code hardcoded
3

This reverts commit 9cf500a3.

This reverts commit b9abecfc.

related #7234

fix pingoff  test race

Fix TLS certificate loading for chained certificates.

Now it is also possible for ACL SETUSER to accept empty strings
as valid operations (doing nothing), so for instance

    ACL SETUSER myuser ""

Will have just the effect of creating a user in the default state.

This should fix #7329.

fix clusters mixing accidentally by gossip

This will likely avoid false positives due to trailing pings.

tests: each test client work on a distinct port range

32bit CI needs to build modules correctly

Revive and adjust meaningful offset tests

these tests create several edge cases that are otherwise uncovered (at
least not consistently) by the test suite, so although they're no longer
testing what they were meant to test, it's still a good idea to keep
them in hope that they'll expose some issue in the future.