Make the service account privileges dynamic i.e. not hardcoded

[TheRubick]

In this PR I have suggested to make the privileges i.e. the verbs/actions that the clusterRole assigned to the service account variable and dynamic not hardcoded.

Why do we need this change? for example if you want the replicator service account to read from all namespaces but just replicate/push to a specific namespace(s) - by creating a rolebinding for this namespace(s) - not for the whole cluster. Also it can be considered as a good security practice where making a service account do anything in the clusterRole, isn't recommended at all.

So I have made the ability to restrict the privileges assigned to the service account.

I need your opinion to resume working on this feature :)

I have mentioned my proposal here in this issue and decided to make it real :)