feat: Allow collecting Telemetry module status metrics in development variant

[shorim]

Description

Changes proposed in this pull request (what was done and why):

• Move the KymaInputAllowed field from the MetricPipeline controller config to the reconciler config, so that it can be passed down to the gateway config builder

• When the feature flag --kyma-input-allowed is true and a MetricPipeline exists with the annotation telemetry.kyma-project.io/experimental-kyma-input set to true, then the Telemetry module status metrics are collected by the Metric Gateway. This is done by running a kymastatsreceiver wrapped inside a singletonreceivercreator

• For the instrumentationScope of the Kyma status metrics, set the name to io.kyma-project.telemetry/kyma and set the version to the value of the module version (same as for other inputs)

• Move the transform processor for setting the instrumentationScope from the internal/otelcollector/config/metric/agent pkg to the internal/otelcollector/config/metric pkg to make it accessible for both the agent and the gateway

• Rename the e2e test label v1beta1 to experimental so that it can be used for labelling tests of all experimental features

• Adjust the creation of the FlatMetric in the e2e testkit to be created for each metric data point and not just one instance for all the metric data points.

• Add unit and e2e tests

Changes refer to particular issues, PRs or documents:

• New metric input for kyma status as annotation #1182

Traceability

• The PR is linked to a GitHub issue.
• The follow-up issues (if any) are linked in the Related Issues section.
• If the change is user-facing, the documentation has been adjusted.
• The feature is unit-tested.
• The feature is e2e-tested.