Add ListResolvableAliases to the user service (#4609)

* Add ListResolvableAliases to the user service

There are a few non common ways this method uses our ACL
and grant system. A user is able to list resolvable
aliases for another user if they are granted permission
to do so. That means we had to load the grants for
the user being listed for and not the requester when
determining if an alias is able to resolve to a destination
for which the requested user has permission.

Similarly, the grant hash used for the list pagination
is required to be that of the user being listed and not
the requester.

internal/daemon/controller/testdata/Test_rateLimiterConfig_writeSysEvent/defaults.json

@@ -3787,6 +3787,32 @@
               "unlimited": false
             }
           ],
+          "list-resolvable-aliases": [
+            {
+              "action": "list-resolvable-aliases",
+              "limit": 30000,
+              "per": "total",
+              "period": "30s",
+              "resource": "user",
+              "unlimited": false
+            },
+            {
+              "action": "list-resolvable-aliases",
+              "limit": 30000,
+              "per": "ip-address",
+              "period": "30s",
+              "resource": "user",
+              "unlimited": false
+            },
+            {
+              "action": "list-resolvable-aliases",
+              "limit": 3000,
+              "per": "auth-token",
+              "period": "30s",
+              "resource": "user",
+              "unlimited": false
+            }
+          ],
           "no-op": [
             {
               "action": "no-op",
@@ -4233,7 +4259,7 @@
           ]
         }
       },
-      "max_size": 336168,
+      "max_size": 338169,
       "msg": "controller api rate limiter"
     },
     "op": "controller.(rateLimiterConfig).writeSysEvent",