Modifying the number of peer pod VMs per node is present in 1.8 but missing from 1.9.

Logically, the procedure cannot be performed until after the kataConfig CR is created, but this placement would result in an optional procedure being introduced very late in the documentation.

I recommend the following changes for ALL platforms that use peer pods:

• Insert the module after Peer pod resource requirements as a subsection (level offset +1). This placement ensures that the procedure is introduced early enough in the documentation and accompanies the correct concept module.
• Update all high-level OSC CLI procedures so that the procedure appears after "Creating kataConfig CR":

Current text:

1. Install the OpenShift sandboxed containers Operator.
2. Optional: Change the number of virtual machines running on each worker node.
3. Optional: Create the peer pods secret if you uninstalled the Cloud Credential Operator, which is installed with the OpenShift sandboxed containers Operator.
4. Optional: Select a custom pod VM image.
5. Create the peer pods config map.
6. Optional: Create the Azure secret.
7. Optional: Customize the Kata agent policy.
8. Create the KataConfig custom resource.
9. Configure the OpenShift sandboxed containers workload objects.

New text:

1. Install the OpenShift sandboxed containers Operator.
2. Optional: Create the peer pods secret if you uninstalled the Cloud Credential Operator, which is installed with the OpenShift sandboxed containers Operator.
3. Optional: Select a custom pod VM image.
4. Create the peer pods config map.
5. Optional: Create the Azure secret.
6. Optional: Customize the Kata agent policy.
7. Create the KataConfig custom resource.
8. Optional: Change the number of virtual machines running on each worker node.
9. Configure the OpenShift sandboxed containers workload objects.