This story is an extension to https://issues.redhat.com/browse/KATA-3969

Idea is to extend the support for IBM SE configuration file.

Ensure the operator manages CRI-O drop-in configuration files for CoCo runtimes (IBM SE) via the RPM.

As a platform engineer, I want CRI-O properly configured for IBM SE CoCo runtime, So that the container runtime can launch confidential workloads with appropriate TEE settings for IBM SE.

  Acceptance Criteria:

  - Generate CRI-O configuration for detected TEE type if it's IBM SE (along with TDX/SNP)

  - Register kata-qemu-se runtime in CRI-O if IBM SE enabled LinuxONE hardware

  - Configure runtime paths to use OSC Extension QEMU

  - Include TEE-specific runtime configuration paths for IBM SE

  - Handle both Single Node OpenShift and multi-node cluster topologies

  Testing Considerations:

  - Unit Tests: CRI-O configuration generation for SE along with other TEEs

  - Unit Tests: MachineConfig generation with correct targeting

  - Integration Tests: MachineConfig deployment and node updates

  - Integration Tests: CRI-O configuration validation on target nodes

  - E2E Tests: Verify CRI-O can launch IBM SE TEE specific runtime

  - Compatibility Tests: Test with different CRI-O versions

  - Rollback Tests: Configuration updates and rollback scenarios

  - SNO Tests: Single Node OpenShift configuration deployment (dependent on IBM linuxone h/w availability)