[Security Solution][Alerts] EQL Sequence "shell" alert is missing kibana.alert.uuid

[marshallmain]

As a result, subsequent rule runs will attempt to write duplicate alerts. The duplicates won't be created, which is good, but they cause errors to be logged such as

ResponseError: {"took":911,"errors":true,"items":[{"create":{"_index":".internal.alerts-security.alerts-infosec-detections-000001","_id":"f3b02017135ce51411a768167836e0ef0bfc587f9a42d002065282a7c8a45c12","status":409,"error":{"type":"version_conflict_engine_exception","reason":"[f3b02017135ce51411a768167836e0ef0bfc587f9a42d002065282a7c8a45c12]: version conflict, document already exists (current version [1])","index_uuid":"ZLAUF8zzTlucc4ZXV-5Swg","shard":"0","index":".internal.alerts-security.alerts-infosec-detections-000001"}}},{"create":{"_index":".internal.alerts-security.alerts-infosec-detections-000001","_id":"1443f53d00d61d6775648f31cf2ed8a527e7d82742ee579de8c78085121c7ada","_version":1,"result":"created","_shards":{"total":2,"successful":2,"failed":0},"_seq_no":135270,"_primary_term":1,"status":201}},{"create":{"_index":".internal.alerts-security.alerts-infosec-detections-000001","_id":"61125124e76afeb4c7130af679266b5b93ad7562f17750cbeb50d9bda57218d8","_version":1,"result":"created","_shards":{"total":2,"successful":2,"failed":0},"_seq_no":135271,"_primary_term":1,"status":201}},{"create":{"_index":".internal.alerts-security.alerts-infosec-detections-000001","_id":"91aa28ba7a4a07afb33a23e34c5828820b4c3e7163587f6c51c89ab5d36fc6ef","_version":1,"result":"created","_shards":{"total":2,"successful":2,"failed":0},"_seq_no":135272,"_primary_term":1,"status":201}}]}
    at /usr/share/kibana/x-pack/plugins/rule_registry/server/rule_data_client/rule_data_client.js:183:29
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at alertWithPersistence (/usr/share/kibana/x-pack/plugins/rule_registry/server/utils/create_persistence_rule_type_wrapper.js:91:32)
    at /usr/share/kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_types/factories/bulk_create_factory.js:37:7
    at eqlExecutor (/usr/share/kibana/x-pack/plugins/security_solution/server/lib/detection_engine/signals/executors/eql.js:106:26)
    at Object.executor (/usr/share/kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_types/eql/create_eql_alert_type.js:80:22)
    at Object.executor (/usr/share/kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_types/create_security_rule_type_wrapper.js:261:29)
    at Object.executor (/usr/share/kibana/x-pack/plugins/rule_registry/server/utils/create_persistence_rule_type_wrapper.js:29:21)
    at TaskRunner.executeAlertInstances (/usr/share/kibana/x-pack/plugins/alerting/server/task_runner/task_runner.js:201:31)
    at promiseResult (/usr/share/kibana/x-pack/plugins/alerting/server/lib/result_type.js:44:17)
    at TaskRunner.loadAlertAttributesAndRun (/usr/share/kibana/x-pack/plugins/alerting/server/task_runner/task_runner.js:375:14)
    at errorAsAlertTaskRunResult (/usr/share/kibana/x-pack/plugins/alerting/server/task_runner/task_runner.js:758:12)
    at TaskRunner.run (/usr/share/kibana/x-pack/plugins/alerting/server/task_runner/task_runner.js:439:9)
    at TaskManagerRunner.run (/usr/share/kibana/x-pack/plugins/task_manager/server/task_running/task_runner.js:272:22)

We should populate kibana.alert.uuid in the EQL sequence shell alerts the same way we populate the field for EQL sequence building block alerts and alerts from other rule types.

This bug also highlights the importance of having a reliable static type system for alerts, which could have caught the missing field easily.

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)