✨ feat: Update CronJob and Multiversion tutorials to use Status Conditions

[nerdeveloper]

• Add Status Conditions support following K8s API conventions
• Implement meta.SetStatusCondition() throughout reconciliation
• Add condition types: Available, Progressing, Degraded
• Update tests to verify Status Conditions behavior
• Add test cases for suspended CronJobs

This aligns the tutorials with best practices demonstrated in the Deploy Image Plugin example, addressing issue #5024 and #4019.

Note: This PR contains manual changes to the tutorial code. The CI will fail as make generate needs updates (will be handled in a follow-up PR per the proposed solution).

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nerdeveloper
Once this PR has been reviewed and has the lgtm label, please assign camilamacedo86 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Hi @nerdeveloper. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[vitorfloriano]

Hi @nerdeveloper, thanks for working on this! While we wait for the maintainer’s review, could you take a look at the failing checks? Getting those fixed should help move things along more smoothly. The Coverage (Coveralls) failure looks like a flake, so no worries there. Let me know if there’s anything I can do to help.

[vitorfloriano]

Hi @nerdeveloper, thanks for fixing the failing checks! Just one more thing: to keep the commit history clean, could you please squash your commits into a single one?