[APM] Switching environments on the Service Error tab causes flaky rendering/request behaviour for detailed_statistics

[Bluefinger]

Kibana version:
8.17.0

Elasticsearch version:
8.17.0

Server OS version:
N/A

Describe the bug:

On services assigned to more than one environment, switching between environments on the Errors tab of the APM Services page for the service in question causes the detailed_statistics request to fire multiple times or not fire at all, occasionally resulting in the page not rendering the details correctly.

Steps to reproduce:

1. Go to APM Services
2. Select a Service with more than one environment + has recorded errors
3. Go to the Errors tab
4. Open browser dev tools and switch to a different environment
5. detailed_statistics request should fire twice, the first aborted with the second succeeding, or not firing at all

Expected behavior:
detailed_statistics should fire only once, like when you first load the Error tab on the default environment.

Screenshots (if relevant):

Any additional context:
This bug is a bit of a heisenbug with regards to whether the page renders correctly or not, but the multiple requests are fairly easy to reproduce versus some of the other potential failures.

[elasticmachine]

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

[cauemarcondes]

5. ..., or not firing at all

Isn't it because the query is cached?

[cauemarcondes]

The aborted request problem happens on many other tabs too, whoever picks this issue could fix it on the other places as well.

[Bluefinger]

5. ..., or not firing at all

Isn't it because the query is cached?

Maybe the request is getting cached incorrectly and remains in an invalid state. I wasn't able to reproduce this one, so this might require a bit more investigation to see if we get invalid cached states.