Update Rust utils to handle nullable log_ingestor configuration

[coderabbitai]

Problem

The Rust utils cannot handle null values for the log_ingestor key in clp_config.yaml and fail with a parsing error.

Impact

When the API server is enabled while log_ingestor is disabled by setting log_ingestor: null, the API server fails to start. This is particularly problematic because the current default configuration in Helm values.yaml has log_ingestor: null, causing the v0.8.0 chart to deploy an API server that continuously crashes and restarts.

Solution

Update the Rust configuration parser to correctly handle nullable log_ingestor values, treating null as an indication that the log-ingestor feature should be disabled.

References

• PR: feat(helm): Add log-ingestor deployment. #1856
• PR: fix(helm): Ensure log_ingestor is explicitly null in configmap when disabled (fixes #1881). #1882
• Related issue: Fix log_ingestor configuration fallback to defaults when set to null in Helm values.yaml #1881
• Comment: feat(helm): Add log-ingestor deployment. #1856 (comment)
• Reported by: @junhaoliao

Files Affected

• Rust configuration parser (likely in components utilizing clp_config.yaml)