[APM] Comparison using expected bounds should not show on individual transactions

[LucaWintergerst]

Kibana version: 8.5.0 BC

Describe the bug:

The ML Job used for the expected bounds comparison is evaluating the overall number of transactions and their latency. It's not split by transaction.name

Therefore when displaying the expected bounds on top of individual transactions, the comparison does not make sense as it's always higher unless the service only has a single transaction.name

Overall Service (this works as expected)

Individual Transaction (this does not work)

Easy fix is to just disable the comparison for the individual views.
Longer term better fix could be to evaluate a multi metric job which splits the results by each unique transaction.name

[elasticmachine]

Pinging @elastic/apm-ui (Team:APM)

[sorenlouv]

@qn895 Thanks for self-assigning. Let me know if I can do anything to help out. Do you think it's possible to get a fix into 8.6 and backport to 8.5?

[gbamparop]

@qn895 do you have all the information that you need for this issue? Are you planning to work on it or you would rather have the APM team work on it?

[qn895]

Closing this via #155915