[APM] [OTel] Make APM UI use service metrics with OTel-native data

[AlexanderWert]

Service overview with OTel native data does not use service metrics.

The time_range_metadata requests returns:

 "isUsingServiceDestinationMetrics": true,
    "sources": [
        {
            "documentType": "serviceTransactionMetric",
            "rollupInterval": "1m",
            "hasDocs": false,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "serviceTransactionMetric",
            "rollupInterval": "10m",
            "hasDocs": false,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "serviceTransactionMetric",
            "rollupInterval": "60m",
            "hasDocs": false,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "transactionMetric",
            "rollupInterval": "1m",
            "hasDocs": true,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "transactionMetric",
            "rollupInterval": "10m",
            "hasDocs": false,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "transactionMetric",
            "rollupInterval": "60m",
            "hasDocs": false,
            "hasDurationSummaryField": false
        },
        {
            "documentType": "transactionEvent",
            "rollupInterval": "none",
            "hasDocs": true,
            "hasDurationSummaryField": false
        }

Potential cause

With OTel-native data we cannot guarantee that service metrics with transaction.duration.summary and transaction.duration.histogram land on the same doc. As a result, we can have all permutations of docs having these two metrics or not:

So we need the change the corresponding check in the UI.

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[AlexanderWert]

Closing as that issue is resolved through proper data ingestion