Logic to set the name in the Kubernetes Role Binding Dekorate is not correct

[Sgitario]

There are two issues in regards to the AddRoleBindingResourceDecorator:

1. We can't set a role binding name like "myname-view", because the logic checks that at least one deployment with the same name exists.
2. If we do not set any role binding name, it will use the name of the first deployment resource found. So, if we provide custom resource that adds at least one additional deployment (for example, with the name "myotherdeployment", the role binding name will use this deployment name plus the role name, which is not consistent with the behavior when not adding custom resources.