chore: fix integration tests v1alpha3 and v1alpha4

[Fortune-Ndlovu]

Description

This PR fixes failing integration tests by registering all API versions (v1alpha1-v1alpha4) in the Kubernetes client scheme, resolving the "no kind is registered for the type v1alpha3.Backstage" error. Additionally, it improves test organization by moving the API compatibility test from config-refresh_test.go to a dedicated cr-compatibility_test.go file, ensuring each test file has a clear, focused purpose.

Which issue(s) does this PR fix or relate to

https://issues.redhat.com/browse/RHDHBUGS-1907

PR acceptance criteria

• Tests
• Documentation

How to test changes / Special notes to the reviewer

Summary by Sourcery

Extract and centralize API version compatibility tests, update test scheme registration, and refresh generated deepcopy code

Enhancements:

• Move v1alpha3 and v1alpha4 compatibility test from config-refresh into its own cr-compatibility_test.go file
• Register v1alpha1, v1alpha2, and v1alpha3 API versions in the integration test suite scheme

Tests:

• Add a dedicated integration test for verifying CR compatibility between v1alpha3 and v1alpha4

Chores:

• Regenerate deepcopy methods for API types v1alpha1 through v1alpha4

[sourcery-ai]

Reviewer's Guide

Refactor integration tests by extracting v1alpha3/v1alpha4 compatibility tests into a dedicated file, register all API versions in the test suite, and regenerate deep-copy code for v1alpha1–v1alpha4.

File-Level Changes

Change	Details	Files
Extracted and removed compatibility tests from config-refresh suite	Deleted mixed v1alpha3/v1alpha4 compatibility It() block Removed v1alpha3 and metav1 imports	integration_tests/config-refresh_test.go
Added standalone compatibility test file	Created dedicated test for v1alpha3 and v1alpha4 coexistence Copied and adapted existing test logic into new file	integration_tests/cr-compatibility_test.go
Registered all API versions in test suite	Imported v1alpha1, v1alpha2, v1alpha3 APIs Called AddToScheme for v1alpha1–v1alpha3 in BeforeSuite	integration_tests/suite_test.go
Regenerated deepcopy code for all API versions	Updated zz_generated.deepcopy.go for v1alpha1–v1alpha4	api/v1alpha1/zz_generated.deepcopy.go api/v1alpha2/zz_generated.deepcopy.go api/v1alpha3/zz_generated.deepcopy.go api/v1alpha4/zz_generated.deepcopy.go

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Fortune-Ndlovu - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.8.0-pr-1451-d9108ec
2. https://quay.io/rhdh-community/operator-bundle:0.8.0-pr-1451-d9108ec
3. https://quay.io/rhdh-community/operator-catalog:0.8.0-pr-1451-d9108ec

[github-actions]

PR images are available:

1. https://quay.io/rhdh-community/operator:0.8.0-pr-1451-945d351
2. https://quay.io/rhdh-community/operator-bundle:0.8.0-pr-1451-945d351
3. https://quay.io/rhdh-community/operator-catalog:0.8.0-pr-1451-945d351

[rm3l]

Thanks.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rm3l]

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