admin api: rename allow/deny api calls in api v2

doc/api/garage-admin-v2.yml

@@ -826,11 +826,11 @@ paths:
               schema:
                 $ref: '#/components/schemas/BucketInfo'
 
-  /BucketAllowKey:
+  /AllowBucketKey:
     post:
       tags:
         - Permissions
-      operationId: "BucketAllowKey"
+      operationId: "AllowBucketKey"
       summary: "Allow key"
       description: |
         ⚠️ **DISCLAIMER**: Garage's developers are aware that this endpoint has an unconventional semantic. Be extra careful when implementing it, its behavior is not obvious.
@@ -886,11 +886,11 @@ paths:
               schema:
                 $ref: '#/components/schemas/BucketInfo'
 
-  /BucketDenyKey:
+  /DenyBucketKey:
     post:
       tags:
         - Permissions
-      operationId: "BucketDenyKey"
+      operationId: "DenyBucketKey"
       summary: "Deny key"
       description: |
         ⚠️ **DISCLAIMER**: Garage's developers are aware that this endpoint has an unconventional semantic. Be extra careful when implementing it, its behavior is not obvious.

doc/drafts/admin-api.md

@@ -705,7 +705,7 @@ Warning: this will delete all aliases associated with the bucket!
 
 ### Operations on permissions for keys on buckets
 
-#### BucketAllowKey `POST /v2/BucketAllowKey`
+#### AllowBucketKey `POST /v2/AllowBucketKey`
 
 Allows a key to do read/write/owner operations on a bucket.
 
@@ -726,7 +726,7 @@ Request body format:
 Flags in `permissions` which have the value `true` will be activated.
 Other flags will remain unchanged.
 
-#### BucketDenyKey `POST /v2/BucketDenyKey`
+#### DenyBucketKey `POST /v2/DenyBucketKey`
 
 Denies a key from doing read/write/owner operations on a bucket.