Add SentinelOne connector

[patrykkopycinski]

Summary

Adds new connector type to support https://www.sentinelone.com/

The scope of this PR was limited to the Connector logic, schemas, and types to make PR more digestible.
In the current PR, the connector is NOT registered, so it's not going to be available to the users.
In the follow-up PR I'm going to improve the UX of Param's form and then enable the connector

visual changes include a screenshot or gif.

[pmuellr]

LGTM, added a note about updating CODEOWNERS, and a brief note on schema.nullable() vs schema.maybe() usage

[pmuellr]

Can you add the sentinelone directories to the CODEOWNERS file, like we did with the gen_ai connector?

kibana/.github/CODEOWNERS

Lines 1143 to 1146 in a42df25

	## Explore owner connectors
	/x-pack/plugins/stack_connectors/public/connector_types/gen_ai @elastic/security-threat-hunting-explore
	/x-pack/plugins/stack_connectors/server/connector_types/gen_ai @elastic/security-threat-hunting-explore
	/x-pack/plugins/stack_connectors/common/gen_ai @elastic/security-threat-hunting-explore

That way, we'll only get pinged for review when the framework code changes ...

[pmuellr]

I always check connector schema for uses of schema.maybe(). You can't use it in connector config or secrets, but it can be used in params, and I don't think we have requirements on the "response" of a connector, since we generally throw it away, only not throwing it away for http invocations (where we return it in the response body).

The usage looks ok here, but thought I'd just double-check that's your understanding as well.

Besides that, these few uses of schema.maybe() look almost out-of-place, with everything else using schema.nullable(). So just thought I'd note that, in case you intended these to be schema.nullable() instead.

[patrykkopycinski]

buildkite test this

[patrykkopycinski]

buildkite test this

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[patrykkopycinski]

buildkite test this

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 561815b

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
triggersActionsUi	538	544	+6

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
triggersActionsUi	88.9KB	89.0KB	+106.0B

Unknown metric groups

API count

id	before	after	diff
triggersActionsUi	564	570	+6

ESLint disabled in files

id	before	after	diff
stackConnectors	4	5	+1

ESLint disabled line counts

id	before	after	diff
stackConnectors	90	93	+3

Total ESLint disabled count

id	before	after	diff
stackConnectors	94	98	+4

History

• 💛 Build #148751 was flaky 752c441
• 💚 Build #148629 succeeded 752c441
• 💚 Build #148566 succeeded 752c441
• 💛 Build #148532 was flaky 752c441
• 💔 Build #148474 failed 76b4a3d413f70c558701d3c496a7e54ee118fc40
• 💛 Build #147048 was flaky 07a62ed85335d9eb8467ec5b8b2b7d422af500b4

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

cc @patrykkopycinski