[Stack Monitoring] Address outstanding ESTF failures

[matschaffer]

We have a number of ESTF failures coming from the stack monitoring api integration suite.

• https://github.com/elastic/kibana/issues?q=is%3Aopen+is%3Aissue+label%3Atest-cloud+label%3Afailed-test+label%3ATeam%3AMonitoring

Many of these come from the FTR api_integration test being run on an unexpected environment (like a cloud deployment).

We should look into why these are failing and either:

• Update the test or ESTF to allow for on-cloud runs of these tests
• Skip these tests on cloud

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[matschaffer]

https://github.com/elastic/observability-dev/pull/1992#issuecomment-1058788348 (internal) contains some notes on how I used the ESTF flakey test runner to validate #105354 and ultimately skip those tests on cloud (#126877).

We should be able to validate the rest via a similar procedure.

[matschaffer]

This is also in a similar ballpark, but I think they're not cloud ESTF runs so the nuance might be different:

https://github.com/elastic/kibana/issues?q=is%3Aopen+is%3Aissue+label%3Afailed-test+sort%3Aupdated-desc+label%3A%22Team%3AInfra+Monitoring+UI%22+monitoring

[jasonrhodes]

Moving this to the backlog for now as we are focusing on higher priority issues at the moment. If this is becoming a lot of work for @liza-mae to keep up with, we should skip the tests and come back to it.