Mapping conflicts in Windows event fields across the System and Windows integrations

# Summary
This enhancement request addresses legitimate mapping conflicts in Windows event fields across the System and Windows integrations. A customer has identified three fields with inconsistent type definitions that cause mapping conflicts in Elasticsearch, particularly when data from multiple integrations is ingested into the same cluster.

# Issues

1. winlog.event_data.Options
Conflict: Type keyword in logs-system.application vs long in logs-system.security
Root Cause: Security data stream explicitly defines as long and has convert processor
Actual Values: Hexadecimal strings like "0x1020"
Correct Type: Should be keyword (hex strings cannot be losslessly converted to long)
2. winlog.event_data.StatusCode
Conflict: Type keyword in logs-system.application vs long in logs-system.security
Root Cause: Security data stream explicitly defines as long and has convert processor
Actual Values: Hexadecimal strings like "0xc00000be"
Correct Type: Should be keyword (NTSTATUS codes are hex strings)
3. winlog.event_data.Id
Conflict: Type keyword in logs-system.system vs object in logs-windows.powershell_operational
Root Cause: PowerShell operational stream uses base object definition while system uses explicit keyword typing
Correct Type: Should be consistently keyword across all streams

No files, tests, or entry points are named. Locate the mappings and processors for winlog.event_data.Options, StatusCode, and Id in the System and Windows integrations, then verify that the resulting definitions are consistent and accept the stated hexadecimal values without Elasticsearch mapping conflicts.

Written by the indexing model from the issue text.