[bug] booting an older ISO causes issues with >= v1.5.0 talos clusters

[rsmitty]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

From a customer, we're seeing an issue with Omni where they're provisioning v1.5.2 clusters in Omni. But, when they do that they were booting a v1.4.7 ISO, expecting it to complete the process by upgrading during install time as normal. However, they were presented this in the logs, which points to Omni generating a v1.5 config and trying to apply that to a v1.4 series and thus failed.

19/12/2023 14:33:58 machine:

19/12/2023 14:33:58     features:

19/12/2023 14:33:58         diskQuotaSupport: true # Enable XFS project quota support for EPHEMERAL partition and user disks.

19/12/2023 14:33:58         kubePrism:

19/12/2023 14:33:58             enabled: true # Enable KubePrism support - will start local load balacing proxy.

19/12/2023 14:33:58             port: 7445 # KubePrism port.

19/12/2023 14:33:58             # # Configure Talos API access from Kubernetes pods.

19/12/2023 14:33:58             # kubernetesTalosAPIAccess:

19/12/2023 14:33:58             #     enabled: true # Enable Talos API access from Kubernetes pods.

19/12/2023 14:33:58             #     # The list of Talos API roles which can be granted for access from Kubernetes pods.

19/12/2023 14:33:58             #     allowedRoles:

19/12/2023 14:33:58             #         - os:reader

19/12/2023 14:33:58             #     # The list of Kubernetes namespaces Talos API access is available from.

19/12/2023 14:33:58             #     allowedKubernetesNamespaces:

19/12/2023 14:33:58             #         - kube-system```

### Expected Behavior

Expected would be that installation/upgrade would happen before the apply-config (if this is possible) and then the config being applied would work successfully.

### Steps To Reproduce

1. Boot old v1.4.x iso
2. Add the node to a cluster, specifying >= v1.5.0 for the version
3. See it fail since we supply a kubeprism patch by default now.

### What browsers are you seeing the problem on?

_No response_

### Anything else?

_No response_