[DOCS] Add TheHive connector to automated Observability case screenshots

[lcawl]

Summary

Relates to #180931

This PR adds TheHive connector to the automated screenshot that is used in https://www.elastic.co/docs/current/serverless/observability/case-settings#create-a-connector

The screenshot automation for that page and for https://www.elastic.co/docs/current/serverless/security/cases-settings#external-incident-management-systems had been turned off per #188997 and #189058
I could not replicate those timeout errors, but I added retry.waitFor around any clicks since that's what seems to be done in https://github.com/elastic/kibana/blob/main/x-pack/test_serverless/functional/test_suites/security/ftr/cases/configure.ts

I have also removed one of the automated screenshots that is no longer required per elastic/security-docs#5859

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[adcoelho]

LGTM but maybe we dont need all the retry.waitFor? The failing tests you linked were only about common-flyout-cancel.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: eec61f9

Failed CI Steps

• FTR Configs #5
• FTR Configs #28
• FTR Configs #100
• FTR Configs #102

Metrics [docs]

✅ unchanged

History

• 💚 Build #237769 succeeded 7527434
• 💔 Build #237518 failed 860d6d0
• 💛 Build #236820 was flaky 1ab44b5
• 💛 Build #236819 was flaky ca3b449
• 💔 Build #236804 failed 35a5026

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