As a Node team engineer, I want the Machine Config Operator to translate ContainerRuntimeConfig API settings into CRI-O storage configuration, so that administrators can manage additional storage locations declaratively without manual node configuration.

Details

Implement MCO support for Advanced Container Storage Configuration API, translating ContainerRuntimeConfig settings into CRI-O storage.conf:

• Render additionalLayerStores configuration into storage.conf
• Render additionalImageStores configuration into storage.conf additionalimagestores array
• Render additionalArtifactStores configuration into storage.conf additional_artifact_stores
• Generate MachineConfig with storage.conf for matching node pools
• Handle single ContainerRuntimeConfig per pool (merge configurations to avoid overrides)

Acceptance Criteria

• MCO controller updated to process additionalLayerStores, additionalImageStores, and additionalArtifactStores fields
• storage.conf generated correctly with all three storage types
• MachineConfig created and applied to matching node pools
• Node reboot triggered for configuration application
• Configuration validation and error handling implemented
• Unit tests added for configuration rendering
• PR merged to openshift/machine-config-operator