feat(edr): OCSF mappers + ingestion for 6 EDR integrations

Every EDR (category: endpoint) integration is now audited for an OCSF mapper.
Six had a fetch command but no mapper — add a bundled OCSF mapper for each,
wire the fetch command as an ingestion source (ingest: results_path/dedup_key
[/incremental_field]) and add the top-level ingestion block. Field mappings
were derived from each vendor's fetch output and cross-referenced against the
demisto/content reference for that vendor.

- carbon-black-cloud: search_alerts (results_path results, dedup id) — 35 fields
- cisco-secure-endpoint: list_events (data, id) — 21 fields
- cybereason: query_malops (malops, guid, incr start_time) — 6 fields
- sophos-central: list_alerts (items, id) — 14 fields
- trend-vision-one: list_alerts (items, id, incr start_datetime) — 19 fields
- withsecure: list_incidents (items, incidentId) — 7 fields

Validated: every manifest passes ParseManifest+ValidateManifest and every mapper
passes ParseMapperFile with all JSONata source_path/field expressions compiling.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

integrations/cisco-secure-endpoint/manifest.yaml

@@ -62,7 +62,7 @@ commands:
     outputs_schema: { properties: {} }
   - id: list_events
     name: cisco-amp-list-events
-    description: "List events."
+    description: "List events. Used for ingestion: results path = data."
     risk: read
     inputs_schema:
       properties:
@@ -70,6 +70,9 @@ commands:
         limit: { type: number, description: "Max events (default 50)" }
       required: []
     outputs_schema: { properties: {} }
+    ingest:
+      results_path: data
+      dedup_key: id
   - id: get_trajectory
     name: cisco-amp-get-trajectory
     description: "Get a computer's device trajectory."
@@ -88,3 +91,8 @@ commands:
       properties: {}
       required: []
     outputs_schema: { properties: {} }
+
+ingestion:
+  command: list_events
+  mapper: list_events
+  default_incident_type: "Cisco Secure Endpoint Event"