Propagate global scrape protocols by allowing for global config setting

[jaronoff97]

Description: Adjusts the TA CRD to allow for setting the global config

Link to tracking Issue(s):

• Resolves Global scrape protocols not propagated to target allocator generated scrape configs #3160

Testing: unit and e2e

Documentation:

[jaronoff97]

I confirmed that running this new operator version resulted in this response from the scrape_configs endpoint (after setting this in the global config)

    receivers:
      jaeger:
          protocols:
            grpc:

      # Collect own metrics
      prometheus:
        config:
          global:
            scrape_interval: 30s
            scrape_protocols: ['PrometheusProto','OpenMetricsText1.0.0','OpenMetricsText0.0.1','PrometheusText0.0.4']
          scrape_configs:
            - job_name: 'otel-collector'
              scrape_interval: 10s
              static_configs:
                - targets: [ '0.0.0.0:8888' ]

    processors:

    exporters:
      debug:
    service:
      pipelines:
        traces:
          receivers: [jaeger]
          exporters: [debug]

{
  "otel-collector": {
    "enable_compression": true,
    "enable_http2": true,
    "follow_redirects": true,
    "honor_timestamps": true,
    "job_name": "otel-collector",
    "metrics_path": "/metrics",
    "scheme": "http",
    "scrape_interval": "10s",
    "scrape_protocols": [
      "PrometheusProto",
      "OpenMetricsText1.0.0",
      "OpenMetricsText0.0.1",
      "PrometheusText0.0.4"
    ],
    "scrape_timeout": "10s",
    "static_configs": [
      {
        "targets": [
          "0.0.0.0:8888"
        ]
      }
    ],
    "track_timestamps_staleness": false
  }
}

[swiatekm]

LGTM, one nitpick about the attribute docstring.