Update ACL rules for Replication

[hieu2102]

1. Add permission for SYNC (required by Dual Channel Replication)
   Dual Channel Replication request a full resync from primary node using SYNC (replication.c#L3187):

static int dualChannelReplHandleReplconfReply(connection *conn, sds *err) {
// excluded for brevity
// ...
    if (connSyncWrite(conn, "SYNC\r\n", 6, server.repl_syncio_timeout * 1000) == -1) {
        dualChannelServerLog(LL_WARNING, "I/O error writing to Primary: %s", connGetLastError(conn));
        return C_ERR;
    }
    return C_OK;
}

2. Update the permissions required by Atomic Slot Migration.
   The set of ACL rules currently mentioned in the doc does not work if the cluster has data:

# configure replication users with the set of ACL rules as mentioned in the docs
cat <<EOF > users.acl
user _r on >hello -@all +psync +replconf +ping +cluster|syncslots
EOF
cat <<EOF > config.sh
export ADDITIONAL_OPTIONS="--aclfile /opt/valkey/users.acl --primaryuser _r --primaryauth hello --loadmodule /opt/valkey-audit/build/libvalkeyaudit.so --audit.enabled yes --audit.events all --audit.command_result_mode all"
EOF
./utils/create-cluster/create-cluster start
./utils/create-cluster/create-cluster create

# write some keys
for i in {0000..9999}; do
    valkey-cli -p 30001 -c set $i $i
done

# execute ASM
tnode="$(valkey-cli  -c -p 30001 cluster nodes | grep master|grep -v myself |head -n 1 | awk '{print $1}')"
valkey-cli -c -p 30001 cluster migrateslots slotsrange 0 0 node $tnode

Log output of the ASM job:

26589:M 13 Jul 2026 07:34:45.785 * New slot import job created: {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0}.
26589:M 13 Jul 2026 07:34:45.786 * Slot migration {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0} state transition: waiting-for-ack -> receiving-snapshot
26589:M 13 Jul 2026 07:34:45.894 # == CRITICAL == This slot-import-target is sending an error to its slot-import-source: '-NOPERM No permissions to access a key' after processing the command 'set'
26589:M 13 Jul 2026 07:34:45.894 * Slot migration {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0} state transition: receiving-snapshot -> cleaning-up
26589:M 13 Jul 2026 07:34:45.895 * Cleaning up slot migration {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0} after failed
26589:M 13 Jul 2026 07:34:45.895 * Slot migration {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0} state transition: cleaning-up -> failed
26589:M 13 Jul 2026 07:34:45.895 # Slot migration {name: b5094a3be505334c4888e62f6054456615db3d0a, operation: import, source_node_id: 73bedc79e32275057cec49e9cc5ff0386054ebd5, slots: 0-0} finished. State: failed, Message: Failed to process command during slot migration. Check logs for more information