When ozone.acl.enabled is set to true, the ACL check logic in OzoneManager#listVolumeByUser ignored the provided userName.
This bug is introduced by my commit
e.g. userA won't be able to use ozone sh volume list --user userB to list userB's volumes when ACL is enabled.
Use userName rather than ProtobufRpcEngine.Server.getRemoteUser() for ACL check.