Having traces enabled and metrics disabled still allows to send metrics via (traces) otelcol's instances

[pmalek-sumo]

With introduction of this change: #1647 the chart has an option to send metrics via otelcol's pods (originally designed to handle tracing traffic).

This happens even when sumologic.metrics.enabled is set to false and sumologic.traces.enabled is set to true.

This goal of this issue is to track a set of (breaking) changes that would go into chart that would change the approach from enabling/disabling particular components (e.g. metrics pipeline, tracing pipeline etc) into enabling/disabling particular use cases (e.g. collecting metrics from kubelet, collecting metrics from instrumentations, collecting traces from apps with particular config/instrumentation etc.)

There's a PR that should resolve the problem with missing default-metrics source URL being present in the cluster when sumologic.metrics.enabled is set to false and sumologic.traces.enabled is set to true: #2182 but that will only fix the implementation bug, it won't affect the API contract within the values.yaml of this chart (e.g. sumologic.metrics.enabled=false shouldn't really send metrics).