Enhance ACL WHOAMI command to display active ACL rules for the current connection

[hwware]

Current ACL WHOAMI can only display the username for the current connection.
It need to call ACL LIST to get the active ACL rules, thus there are 2 disadvantages:

1. CALL 2 commands to get ACL rules for the current connection
2. ACL LIST will display all users and their ACL rules, it is not necessary,

This PR allows the current connection to call once "ACL WHOAMI FULL" to get all information.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.98%. Comparing base (2c9db1a) to head (8b23382).

Additional details and impacted files

@@             Coverage Diff              @@
##           unstable    #1821      +/-   ##
============================================
- Coverage     71.03%   70.98%   -0.05%     
============================================
  Files           123      123              
  Lines         65665    65672       +7     
============================================
- Hits          46645    46618      -27     
- Misses        19020    19054      +34     

Files with missing lines	Coverage Δ
src/acl.c	90.74% <100.00%> (+0.04%)	⬆️
src/commands.def	100.00% <ø> (ø)

... and 12 files with indirect coverage changes

[hpatro]

What's the use case for this ?

[madolson]

I generally don't like variadic arguments that change the type of response. So would also somewhat prefer another command.

Also, do we want this to be a variant of ACL GETUSER instead? Somewhat related to this issue, #1807.

[hwware]

Another command? you mean a new command? I am afraid the user need to remember one more.
I guess this command is not same as ACL GETUSER, because this command only apply to current connection, even user do not know the username either.

[madolson]

I guess this command is not same as ACL GETUSER, because this command only apply to current connection, even user do not know the username either.

A new command, like ACL GETMYSELF, is what I'm suggesting. I agree it's one more command.

[hwware]

What's the use case for this ?

As the top comment describe, I thought

[hpatro]

What's the use case for this ?

As the top comment describe, I thought

I mean it's not an expensive operation and don't see what's the pain behind doing it one after another.