Dealing with existing `kata-oc` MCP during upgrade

Description

After upgrading OSC from 1.2 to 1.3, an existing `kata-oc` MCP lacks a label that is used to implement KataConfig.spec.logLevel handling.

Steps to reproduce

<What actions did you take to hit the bug?>
1. Install 1.2 on 4.10
2. Upgrade to 1.3
3.

Expected result

`kata-oc` MCP has the `pools.operator.machineconfiguration.openshift.io/kata-oc` label.

Actual result

`kata-oc` MCP is missing the `pools.operator.machineconfiguration.openshift.io/kata-oc` label.

Impact

This prevents controlling crio-s log level with KataConfig.spec.logLevel.

Env

<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

Additional helpful info

<logs, screenshot, doc links, etc.>