chore: Update manifests after automerge

clusters/cl01tl/manifests/rook-ceph/CustomResourceDefinition-cephobjectstoreusers.ceph.rook.io.yaml

@@ -244,6 +244,19 @@ spec:
                         x-kubernetes-map-type: atomic
                     type: object
                   type: array
+                opMask:
+                  description: The op-mask of the user.
+                  items:
+                    description: 'Internally, RGW labels "operations" on persistent state as `RGW_OP_TYPE_READ` (`read`), `RGW_OP_TYPE_WRITE` (`write`), or `RGW_OP_TYPE_DELETE` (`delete`). All RGW users have an "operation mask", which does not function as mask or filter as is typically implied by the word "mask", but as a set of allowed or permissible "operation" types the user is able to perform. The "operation mask" is applied regardless of the bucket or IAM policy. For example, in order for an RGW user to be able to read an object from a bucket, that user must have **both** the `read` "op mask" bit and an IAM/bucket policy that allows `s3:GetObject`. The default operations allowed are `read`, `write`, and `delete`. Setting the value to `[]` (an empty YAML sequence) causes all "operations" in the mask to be removed, meaning that the user will not be able to perform any operations. These operation masks are supported: `read`, `write`, `delete`'
+                    enum:
+                      - read
+                      - write
+                      - delete
+                    type: string
+                  maxItems: 3
+                  minItems: 0
+                  type: array
+                  x-kubernetes-list-type: set
                 quotas:
                   description: ObjectUserQuotaSpec can be used to set quotas for the object store user to limit their usage. See the [Ceph docs](https://docs.ceph.com/en/latest/radosgw/admin/?#quota-management) for more
                   nullable: true