[HiranmoyChowdhury]

Adds allow_slot / block_slot filter rules, so commands can be kept or dropped by the hash slot of their keys:

[filter]
allow_slot = ["0-5460", "15627"]

Both are empty by default, so nothing changes unless you set them. Commands without keys aren't affected.

Why: I'm replaying per-shard AOF files into a cluster for point-in-time recovery. If slots moved between shards (reshard/rebalance) during that period, the source shard's migration DEL can wipe keys already restored from the destination shard, or the replay hits BUSYKEY. The result depends on replay order. Limiting each shard's replay to the slots it owned at the target time fixes it.

This is possible with a Lua function using SLOTS too, but a built-in rule is simpler and matches the other allow/block filters.

Tested on a 3-shard cluster with a reshard and rebalance during writes. Without the rule, about 1,000 keys went missing or had wrong values after restore. With it, every key matched, in any replay order.

Signed-off-by: HiranmoyChowdhury hiranmoy.das70@gmail.com