Add version logging to upgrade/downgrade tests

[cardil]

Problem

The upgrade tests are hard to debug. Especially the upgrade/downgrade steps do not report anything on success, so it's hard to tell if we upgraded to 1.37.1 (as expected) or maybe 1.38.0.

Solution

Added comprehensive version logging to test/upgrade/installation/serverless.go to report:

• Target CSV and component versions at start
• InstallPlan approval
• CSV success state
• Each component version upgrade/downgrade progress
• Final completion with version confirmation

Example Output

Now when tests run, you'll see clear output like:

🔄 Starting Serverless upgrade to CSV: serverless-operator.v1.37.1 (source: serverless-operator, channel: stable)
   Target versions - Serving: 1.18.0, Eventing: 1.18.0, Kafka: 1.15.0
   Approving InstallPlan: install-abc123
✅ CSV serverless-operator.v1.37.1 is now in Succeeded state
   Waiting for KnativeServing to reach version: 1.18.0
✅ KnativeServing is now at version: 1.18.0
   Waiting for KnativeEventing to reach version: 1.18.0
✅ KnativeEventing is now at version: 1.18.0
   Waiting for KnativeKafka to reach version: 1.15.0
✅ KnativeKafka is now at version: 1.15.0
✅ Serverless upgrade completed successfully to CSV: serverless-operator.v1.37.1

This makes it immediately clear whether the upgrade went to the expected version or an unexpected one.

Assisted-by: 🤖 Claude Opus/Sonnet 4.5

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[cardil]

/cherrypick main
/cherrypick release-1.38

[openshift-cherrypick-robot]

@cardil: once the present PR merges, I will cherry-pick it on top of main, release-1.38 in new PRs and assign them to you.

Details

In response to this:

/cherrypick main
/cherrypick release-1.38

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.

[cardil]

/retest

[cardil]

The fail (flaky) should be fixed with #3973

/hold

[cardil]

/unhold