Hardcoded community configuration in Turtles v0.26.2-rc.x

# Description As reported by @cpinjani @thehejik, Turtles v0.26.2-rc.x Prime seems to be using the community configuration. At some point in the release process the prime-specific configuration file is not embedded in the Turtles prime image, which breaks community/prime differentiation. This is the `clusterctl-config` ConfigMap for a Prime installation of Rancher v2.14.2-alpha5 (Turtles v0.26.2-rc.2), which corresponds to what is expected from a Community version: ``` $ kubectl describe configmap -n cattle-turtles-system clusterctl-config Name: clusterctl-config Namespace: cattle-turtles-system Labels: app.kubernetes.io/managed-by=Helm Annotations: meta.helm.sh/release-name: rancher-turtles meta.helm.sh/release-namespace: cattle-turtles-system Data ==== clusterctl.yaml: ---- images: cluster-api: repository: stgregistry.suse.com/rancher providers: - name: cluster-api type: CoreProvider url: https://github.com/kubernetes-sigs/cluster-api/releases/v1.12.7/core-components.yaml ```