Add await on deletion queries that are blowing up in FTR tests

[delanni]

Summary

We've seen several cases of FTR tests dying of unhandled promise rejections. (https://buildkite.com/elastic/kibana-on-merge/builds/44936#018f56c3-184a-4cd6-98fc-4342d713e52a)

I've managed to locate the place where these requests come from - ideally with this addition, the tests should fail earlier, and not way after the test have been marked successful.

Further problems/questions:

• The FTR runner should not mark these runs successful if there are unhandled promise rejections, rather wait for the promises to settle before concluding
• Why did this call suddenly start to fail?

[delanni]

/ci

[delanni]

cc: @elastic/kibana-cloud-security-posture

[delanni]

/ci

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 502c369

Metrics [docs]

✅ unchanged

History

• 💚 Build #208692 succeeded 502c369

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[opauloh]

Thanks @delanni

We haven't spotted this as the FTR runner was marking these runs as successful as you pointed out, I saw we have other tests under x-pack/test/cloud_security_posture_api/routes with the same behavior, I am going to add an issue for us to handle that