Move the lifecycle tests with to each component module

[dmitryax]

Move lifecycle tests from cmd/otelcolcontrib to each module as individual generated tests.

mdatagen tool can be used for to generate the tests. We would need another section in the metadata.yaml as a source for the generated tests. Sample section:

tests:
  config: // {} by default
    endpoint: http://127.0.0.1
    region: local
    queue:
      enabled: false
    retry:
      enabled: false
  skip_lifecycle: false // false by default
  expect_consumer_error: true // false by default

Moving the tests to the components provides us exposure to the internals of the component, which can help us improve the test coverage and eliminate the need for the 'skip_lifecycle' option. Presently, certain components cannot accommodate test configurations that pass lifecycle tests, hence the necessity of retaining the 'skip_lifecycle' option. Looking ahead, we should be able to utilize internal helpers, not accessible through the public config interface, to ensure proper lifecycle validation and consequently eliminate the need for 'skip_lifecycle'."

[atoulme]

#29284 has shown how to do this and we can now extend this work to all exporters, for starters.

Adding a task list for all exporters:

• alertmanagerexporter
• alibabacloudlogserviceexporter
• awscloudwatchlogsexporter
• awsemfexporter
• awskinesisexporter
• awss3exporter
• awsxrayexporter
• azuredataexplorerexporter
• azuremonitorexporter
• carbonexporter
• cassandraexporter
• clickhouseexporter
• coralogixexporter
• datadogexporter
• datasetexporter
• dynatraceexporter
• elasticsearchexporter
• f5cloudexporter
• fileexporter
• googlecloudexporter
• googlecloudpubsubexporter
• googlemanagedprometheusexporter
• honeycombmarkerexporter
• influxdbexporter
• instanaexporter
• kafkaexporter
• kineticaexporter
• loadbalancingexporter
• logicmonitorexporter
• logzioexporter
• lokiexporter
• mezmoexporter
• opencensusexporter
• opensearchexporter
• prometheusexporter
• prometheusremotewriteexporter
• pulsarexporter
• sapmexporter
• sentryexporter
• signalfxexporter
• skywalkingexporter
• splunkhecexporter
• sumologicexporter
• syslogexporter
• tanzuobservabilityexporter
• tencentcloudlogserviceexporter
• zipkinexporter

For each exporter, you need to take the configuration they expose in cmd/otelcontribcol/exporters_test.go, and move it to a yaml fragment in each of the metadata.yaml of the component under tests/config. Same for skip_lifecycle and expect_consumer_error.