Harmonize the RBAC kubebuilder markers in telemetry manager

[rakesh-garimella]

Description

We have mentioned bunch of the rbac rules via kubebuilder markers and these are not clear as to which rule is for what purpose. These rules can be refactored in such a way they are mentioned where these rules are actually needed.

However during this task we should also refactor the code in rbac.go, such that we could have rbac rules clearly mentioned as to for which receiver/processor etc these rules are for.

Currently kubebuilder annotations are not clear and difficult follow as to which roles are required for which resource.
We can remove these annotations from the controller and create multiple roles belonging to which component or feature.

Criterias:

• The rbacs are refactored in such a way there clear for which components they are needed
• The annotations are removed and we handle these in kustomize with proper documentation. May be by creating seaparate roles ?