Implement deploymentMode Configuration via the osc-feature-gates ConfigMap

User Story
As an administrator, I want to choose a deployment strategy using the deploymentMode key in the osc-feature-gates ConfigMap, so that I can install Kata correctly on clusters with or without the Machine Config Operator (MCO).

Description
This story covers the logic for the operator to read the deploymentMode key from the existing osc-feature-gates ConfigMap. This key accepts specific values (MachineConfig, DaemonSet, DaemonSetFallback) that determine how the operator will install and configure the Kata runtime. This provides the flexibility needed to support different cluster types, such as ROKS and Hypershift which do not use the MCO.

Acceptance Criteria

• The operator reads the deploymentMode key from the osc-feature-gates ConfigMap in the operator's namespace.

• The parsing logic correctly handles the three valid string values: MachineConfig, DaemonSet, and DaemonSetFallback.

• If the value is DaemonSetFallback, the operator correctly checks for the presence of the MCO to determine the final deployment method.

• Invalid values are handled gracefully, logging an error and using a safe default.

• If the deploymentMode key is missing, the operator defaults to MachineConfig mode for backward compatibility.

Configuration Example

 
apiVersion: v1kind: ConfigMapmetadata:name: osc-feature-gatesnamespace: openshift-sandboxed-containers-operatordata:# To force the DaemonSet installation method on all clusters:deploymentMode: "DaemonSet"