Make error when submitting command in incorrect context more explicit

Fix potential memory leak of rioWriteBulkStreamID().

Related to #6054.

Related to #6110.

Enhance IO Threaded: use main thread to handle read/write work

So error message `ERR only (P)SUBSCRIBE / (P)UNSUBSCRIBE / PING / QUIT allowed in this context` will become
`ERR 'get' command submitted, but only (P)SUBSCRIBE / (P)UNSUBSCRIBE / PING / QUIT allowed in this context`

Rename rdb when replica finish receiving rdb asynchronously

We exit later, so no bug fixed, but it is more correct.

See #6054, thanks to @ShooterIT for finding the issue.

Fix bug on KEYS command where pattern starts with * followed by \x00

Update to directive in redis.conf (missing s)

Blocking XREAD[GROUP] should always reply with valid data (or timeout)

Add support for incremental build with header files

Fix petential cluster link error.

Add REDISMODULE_CTX_FLAGS_MULTI_DIRTY.

typo fix in acl.c

Adjusts 'io_threads_num' max in config.c

Sentinel: avoid sentinel changes promoted_slave to be its own replica.

Fixes #6744.

Instead of 512, use the defined max from networking.c

Likely fix #6723.

This is what happens AFAIK: we enter the main loop where we expire stuff
until a given percentage of keys is still found to be logically expired.
There are however other potential exit conditions.

However the "sampled" variable is not always incremented inside the
loop, because we may found no valid slot as we scan the hash table, but
just NULLs ad dict entries. So when the do/while loop condition is
triggered at the end, we do (expired*100/sampled), dividing by zero if
we sampled 0 keys.