commands/.../cmdutil: deduplicate updateRoleForResource and support ClusterRole

[AlexNPavel]

Description of the change: This moves updateRoleForResource to cmdutil so all of the command libraries can use it and also adds support for ClusterRoles in said function.

Motivation for the change: Deduplication of code and supporting users who want to use ClusterRole

[hasbro17]

@shawn-hurley For more context this is to support updating deploy/role.yaml if the type is ClusterRole.
We don't generate that to be a ClusterRole by default but a user may change that.
Some operators using the SDK already do that.
https://github.com/operator-framework/operator-marketplace/blob/master/deploy/rbac.yaml#L1

And we still want the add api command to successfully update the rbac rule for that resource.

[hasbro17]

Seems good to me. Although I'm thinking we should move commands/operator-sdk/cmd/cmdutil/util.go to commands/operator-sdk/cmd/internal/cmdutil/util.go.
Since we don't want to expose these utils outside of the SDK.

[shawn-hurley]

This is a nit, but I always get worried about util packages.

Avoid meaningless package names. Packages named util, common, or misc provide clients with no sense of what the package contains

https://blog.golang.org/package-names

moving it to internal obviosuly helps but it does appear we have multiple unrelated things happening in this package now. And we should just be careful IMO.

I wonder if this code is better suited in the scaffold, as it is neccessary when you scaffold CR's? Or maybe we make the generation of CRD an Exposed function that the ansible new could call?

[AlexNPavel]

@shawn-hurley Do you think this is good for now until we decide how to handle the util packages?

[estroz]

LGTM

[hasbro17]

@shawn-hurley updateRoleForResource() could possibly go in pkg/scaffold/util.go or probably better pkg/scaffold/rbac/rbac.go. Or we can revisit this later if you think it doesn't fit there.

[AlexNPavel]

We will follow up on moving the cmdutil files in #649