feat: Allow setting dedicated Kapsule control-plane flavor (Dedicated-4/8/16) from Crossplane

[jordandubu]

Describe the problem

I’d like to run our Kapsule clusters on the Dedicated-* control-plane tiers (e.g. “Dedicated‑4”) so we get the higher SLA and audit logs. In the Scaleway console/API I can pick those tiers, but when managing the cluster via Crossplane the CRD only accepts type: kapsule. If I change spec.forProvider.type to DEDICATED_4 the cluster is rejected (Crossplane errors with invalid enum value). As a result we can only provision the mutualized control plane.

Reproduction steps

Install provider-scaleway v0.4.0.
Create/update a cluster resource:
apiVersion: k8s.scaleway.upbound.io/v1alpha1
kind: Cluster
metadata:
name: sandbox
spec:
forProvider:
name: sandbox
type: DEDICATED_4 # control-plane flavor we need
region: fr-par
projectId: …
Apply the manifest.
Expected behavior

The cluster is created with the Dedicated‑4 control plane (same as choosing “Dedicated‑4” in the Scaleway console).

Actual behavior
│ Message: apply failed: scaleway-sdk-go: invalid argument(s): type is wrongly formatted, invalid cluster type: │
│ Reason: ApplyFailure │
│ Status: False

What I’d like

Expose the Kapsule control‑plane flavor in the Crossplane provider (either by widening the accepted values for spec.forProvider.type or by introducing a dedicated field). Possible values should match the console: MUTUALIZED, DEDICATED_4, DEDICATED_8, DEDICATED_16.

Thanks a lot!