Allow merging multiple ContainerRuntimeConfig including priorities

1. Proposed title of this feature request
Allow merging multiple ContainerRuntimeConfig including priorities

2. What is the nature and description of the request?
Based on Creating a ContainerRuntimeConfig CR to edit CRI-O parameters it's not possible to have more than one ContainerRuntimeConfig per MachineConfigPool. Instead, all configuration needs to be applied in one ContainerRuntimeConfig and thus changes will require a re-apply of the configuration or complex modification of the existing ContainerRuntimeConfig is required.

It's therefore requested to allow creating multiple ContainerRuntimeConfig per MachineConfigPool and have them merged during MachineConfig rendering. This will allow easy modification of ContainerRuntimeConfig as changes can be simply added or removed by creating/deleting ContainerRuntimeConfig.

In addition to the above request, it should also be possible to assign priorities to ContainerRuntimeConfig in order to have a potentially global ContainerRuntimeConfig for all MachineConfigPool and then overwrite it with specific prioritization for specific MachineConfigPool. Again using the merge functionality to apply everything assigned to the MachineConfigPool but overwriting certain object based on the priority set.

3. Why does the customer need this? (List the business requirements here)
For proper GitOps management it's required to allow multiple ContainerRuntimeConfig per MachineConfigPool to ease the overall management. Requiring to modify existing ContainerRuntimeConfig is rather cumbersome and will need specific logic in the GitOps process that is not expected and desired.

4. List any affected packages or components.
MachineConfigOperator with ContainerRuntimeConfig