Maintain order in AclSetuserArgs

[RohanNagar]

Make sure that:

• You have read the contribution guidelines.
• You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.

Closes #1847.

@mp911de this is my attempt at fixing the bug #1847. I added internal private classes that represent each type of argument and they all inherit from a private interface SetuserArg, which has a build method that adds the argument. AclSetuserArgs then just maintains a List of SetuserArg which allows for maintaining order when adding arguments.

A few other things fixed in this change:

• Previously, AclSetuserArgs was always adding the off argument if none of on() or off() were called. This could result in a bug where a user of the client would expect something like AclSetuserArgs.Builder.addPassword("pass") to not change the on/off state. Now, on or off arguments will only be added if they are added to the builder.
• Previously, if you used the reset() option on AclSetuserArgs, then no other arguments would be added to the command. Redis allows for a command like: acl setuser test reset on +hello. Such a command would first reset the user to a newly created state, and then turn it on and allow the hello command. This has been fixed so that any commands can be included with the reset command.
• The resetpass argument was missing, I have added that argument here as well.

Please let me know what you think about this change. Thank you!

[mp911de]

Great work, it's exactly what we discussed. I'm going to take this PR from here.

[mp911de]

Thank you for your contribution. That's merged, polished, and backported now.