Fix sylva unit status when workload cluster created by gitops

What does this MR do and why?

• A new version of the Sylva unit release operator is used to fix a bug about sylva-units-status preventing workload cluster deployment to succeed

Related reference(s)

• Sylva unit release operator MR: sylva-projects/sylva-elements/sylva-units-operator!206 (merged)
• Ticket: sylva-projects/sylva-elements/sylva-units-operator#19 (closed)

Test coverage

• Manual deployment of a workload cluster with gitops ✅

> k -n teama get sylvaunitsrelease wc1 -o yaml
(...)
status:
  conditions:
  - lastTransitionTime: "2024-11-19T16:26:47Z"
    message: Successfully reconciled sylvaUnitsRelease
    observedGeneration: 1
    reason: ReconciliationSucceeded
    status: "True"
    type: Ready
  observedGeneration: 1
  resourcesStatus:
  - kind: Namespace
    name: teama--wc1
    status: Resource is Ready
  (...)
  - kind: Kustomization
    name: sylva-units-status
    status: Resource is Ready

Backward compliance

• capd: ✅, see https://gitlab.com/sylva-projects/sylva-core/-/pipelines/1551579531
• capo: ✅, see https://gitlab.com/sylva-projects/sylva-core/-/pipelines/1551579451
• capm3: ✅, see https://gitlab.com/sylva-projects/sylva-core/-/pipelines/1551579400