Redis [BUG] ACL SETUSER ... reset doesn't revert to true defaults

Describe the bug

ACL SETUSER with the reset argument doesn't return to the exact defaults as those of a newly-created user. Specifically, the sanitize-payload that is implicitly added by sanitize-dump configuration directive (default: clients) is added. I'm not entirely clear about all the implications, but this irks me, so low-level priority for sure :)

To reproduce

127.0.0.1:6379> ACL SETUSER example
OK
127.0.0.1:6379> ACL LIST
1) "user default on nopass ~* &* +@all"
2) "user example off resetchannels -@all"
127.0.0.1:6379> ACL SETUSER example reset
OK
127.0.0.1:6379> ACL LIST
1) "user default on nopass ~* &* +@all"
2) "user example off sanitize-payload resetchannels -@all"

Expected behavior

The sanitize-payload shouldn't be there - reset means reverting to default.

Comment From: enjoy-binbin

i see in acl setuser reset, this was added in #7807 (i'm guessing oran is going to end his vacation soon) we need to add a test that make sure acl setuser user equal acl setuser user reset

    } else if (!strcasecmp(op,"reset")) {
        serverAssert(ACLSetUser(u,"resetpass",-1) == C_OK);
        serverAssert(ACLSetUser(u,"resetkeys",-1) == C_OK);
        serverAssert(ACLSetUser(u,"resetchannels",-1) == C_OK);
        if (server.acl_pubsub_default & SELECTOR_FLAG_ALLCHANNELS)
            serverAssert(ACLSetUser(u,"allchannels",-1) == C_OK);
        serverAssert(ACLSetUser(u,"off",-1) == C_OK);
+        serverAssert(ACLSetUser(u,"sanitize-payload",-1) == C_OK);
        serverAssert(ACLSetUser(u,"clearselectors",-1) == C_OK);
        serverAssert(ACLSetUser(u,"-@all",-1) == C_OK);
    } else {