Operator Compute resources for log agent and metric agent should be separated

[andreivaloshyn]

Now we can set up compute resources only for entire agent

apiVersion: monitoring.grafana.com/v1alpha1
kind: GrafanaAgent
metadata:
  name: grafana-agent
  labels:
    app: grafana-agent
spec:
  image: grafana/agent
  resources:
    requests:
      cpu: {{ GRAFANA_AGENT_RESOURCE_CPU_MIN }}
      memory: {{ GRAFANA_AGENT_RESOURCE_MEMORY_MIN }}
    limits:
      cpu: {{ GRAFANA_AGENT_RESOURCE_CPU_MAX }}
      memory: {{ GRAFANA_AGENT_RESOURCE_MEMORY_MAX }}
....

and it will be applied for Metric StatefulSet and Log DaemonSet which sometimes can be inconvenient

[captncraig]

A workaround for this would be to have multiple GrafanaAgent resources for each use case. One for metrics and one for logs. It sounds a little annoying, but it would functionally be the same thing.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity in the past 30 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed in 7 days if there is no new activity.
Thank you for your contributions!