[Epic] ECS GenAI Field Support for Security Detections

## Description

TRaDE is starting to build detections on [ECS GenAI](https://www.elastic.co/docs/reference/ecs/ecs-gen_ai) fields. Current integrations do not have comprehensive support for `gen_ai` fields. We are requesting, where available, the following fields be collected/parsed in GenAI integrations. In most cases the data is already available but not being parsed. In two cases (Anthropic/OpenAI) new data streams would need to be added. In the case of Cursor, at this time it is best handled at the endpoint, so no issue is being opened.

```
gen_ai.provider.name
gen_ai.request.model
gen_ai.response.model
gen_ai.request.max_tokens
gen_ai.request.temperature
gen_ai.request.seed
gen_ai.request.stop_sequences
gen_ai.operation.name
gen_ai.conversation.id (OTel)
gen_ai.usage.input_tokens
gen_ai.usage.output_tokens
gen_ai.token.type
gen_ai.response.finish_reasons
gen_ai.input.messages
gen_ai.output.type
gen_ai.output.messages
gen_ai.response.id
gen_ai.system_instructions
gen_ai.tool.definitions
gen_ai.tool.call.id
gen_ai.tool.name
gen_ai.tool.type
gen_ai.tool.call.result
gen_ai.tool.call.arguments
file.path (if anything exists, for tool calls)
destination.address (if possible, for tool calls)
```

## Messages/thinking blocks

For chain of thought analysis, it is important that each integration document how to collect both `gen_ai.input.messages` and `gen_ai.output.messages` where they are available, along with thinking summaries for `output.messages`.

In each issue below, I have a more detailed analysis for each field per integration, as not all fields will be available for each one.