[ResponseOps][Connectors] Fixing flaky connectors·ts test

[doakalexi]

Resolves https://github.com/elastic/kibana/issues/88796

Summary

Removed the skip on the tests in connectors·ts Flaky test run https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1283#_

Checklist

• [x] Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[kibana-ci]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 4d8e06e194282446f5ae7ce8a415846214d914e4

Metrics [docs]

✅ unchanged

History

• :broken_heart: Build #74614 failed fd82d22bc11336509b8b1585f58ee523e550bad7
• :green_heart: Build #74437 succeeded 6bac31adfdd38d77156a52e1d1c10acc20326726
• :green_heart: Build #74174 succeeded 41b5d169c463ae409b7eb48d3f0f9ea7e1804f5d
• :broken_heart: Build #74140 failed 4440698dcea03dfece50a2d4f543c12ccfac2404
• :green_heart: Build #73992 succeeded 9f760d8a43f6817057375b5dac725ffe559397a1

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

[doakalexi]

Can you delete many things like this, or just Plugins? @wayneseymour You can delete many things. This is being used for alerting and actions, but you can reuse the same paradigm for anything with an HTTP api.

[wayneseymour]

Can you delete many things like this, or just Plugins? @wayneseymour You can delete many things. This is being used for alerting and actions, but you can reuse the same paradigm for anything with an HTTP api.

oh snap!!! thanks so very much! cc/ @LeeDr