feat: Forward Redfish diagnostic payloads from health logs

[jayzhudev]

Is this a new feature, an enhancement, or a change to existing functionality?

Enhancement

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

The health crate currently forwards Redfish SSE and periodic log records, but diagnostic payload fields such as DiagnosticData, CPER payloads, and AdditionalDataURI are not available to downstream log consumers.

Feature Description

The health crate does not need to be aware of the schemas for these payloads and can treat the payloads as opaque log data to let downstream OTLP, tracing, file, or other consumers to interpret.

For SSE and periodic Redfish logs:

• Detect DiagnosticData, DiagnosticDataType, OEMDiagnosticDataType, AdditionalDataURI, and size metadata.
• Create a supplemental LogRecord when diagnostic data or URI metadata is present.
• Use the diagnostic payload as the supplemental record body when present.
• Add Redfish metadata attributes such as diagnostic type, URI, parent message id, event id, and log entry id.

For sinks:

• Add include_diagnostics option to tracing, log file, and OTLP sink configs.
• Keep default behavior unchanged.
• When enabled, emit supplemental diagnostic records.
• For OTLP, preserve existing parent-log dedup behavior and append diagnostic records without deduplication.
• Use bounded in-process backpressure for OTLP diagnostic records; this is not required to be durable across restarts.

Describe your ideal solution

No response

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

• I agree to follow NVIDIA Infra Controller's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request