⚠️ Align Status fields to optionalfields API conventions

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Part of #10852

[sbueringer]

/test pull-cluster-api-e2e-main

[sbueringer]

/test pull-cluster-api-e2e-main

[JoelSpeed]

/lgtm

In each of these cases, adding MinProperties means we can't do status: {} as this would violate the min properties validation. We therefore need structured clients to not render status: {} in a marshalled object, which is where omitzero will help us.

This seems aligned with the intentions of optional fields

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: fb960772283c7cc759e928d6c8eb9b963e4820ad

[fabriziopandini]

/lgtm
/approve

/hold (we are going to merge optionalfields PR in order to minimize conflicts)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [fabriziopandini]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

/hold cancel