Crawl connectors, which finds all recently updated connector instances

[erikcurrin-elastic]

Summary

Implement a crawler for connectors that recreates the SML entries for them

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[kderusso]

This task runner is shared by all attachment types, so every crawl will depend on the hidden action type being registered.Do we want this type of access for non-connector crawls? Should they be scoped to only connector crawls?

Can we please add some tests that handle when action mappings are not preasent?

[erikcurrin-elastic]

Fiddled with this, we can have the definition have an array for this (hiddenTypes I guess?). Then connectors is the only thing that sets it.

[github-actions]

Reviewed the connector SML crawler change. The list crawler, the requiredHiddenTypes plumbing into createInternalRepository, and the added test coverage are sound and consistent with the crawler security model. One inline note on a now-stale doc comment.

Generated by Claude Reviewer for #280592 · 19.9 AIC · ⌖ 0.815 AIC

[kibanamachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: e04a435
• Build duration: 62 mins

Failed CI Steps

• Scout Lane #6 - stateful-classic / default

Test Failures

• [job] [logs] Scout Lane #6 - stateful-classic / default / local-stateful-classic - Entity attachment cases – flyout add-to-case actions and Entities accordion - Entities accordion renders when entity attachments were added via API
• [job] [logs] Scout Lane #6 - stateful-classic / default / local-stateful-classic - Entity attachment cases – flyout add-to-case actions and Entities accordion - renders no Entities accordion when a case has no entity attachments

Metrics [docs]

✅ unchanged

History

• 💚 Build #475564 succeeded c858a39
• 💛 Build #475276 was flaky 26b8f9f
• 💛 Build #474976 was flaky 52852fa