Role binding for bento requests references incorrect yatai-system namespace

[nrlulz]

Since updating to yatai-image-builder v1.2.55 I have encountered the following error when attempting to modify a bento deployment from yatai:

deploy deployment revision: failed to deploy kube bento deployment: failed to get kube bento request: bentorequests.resources.yatai.ai "bentorequest-name-here" is forbidden: User "system:serviceaccount:yatai-system:yatai" cannot get resource "bentorequests" in API group "resources.yatai.ai" in the namespace "yatai"

I have what I believe to be the default configuration - yatai and its service account live in the yatai-system namespace, and bentos are deployed to the yatai namespace. The role binding references a service account in the namespace where the bentorequest lives (yatai in this case), which doesn't exist. I believe it should point to the yatai-system namespace. It would happen to work as-is if everything were deployed to the same namespace. I have worked around this in the meantime by enabling bentoRequestAllNamespaces.

I'm guessing the change that needs made is something like this:

https://github.com/bentoml/yatai-image-builder/blob/v1.2.55/helm/yatai-image-builder/templates/rolebinding-yatai-with-bento-request.yaml#L14

  name: {{ $.Values.yataiSystem.serviceAccountName }}
-  namespace: {{ . | quote }}
+  namespace: {{ $.Values.yataiSystem.namespace | quote }}
{{- end }}