PWX-27076: Migrate CRD objects from the same group for a which CR exists.

[adityadani]

What type of PR is this?

improvement

What this PR does / why we need it: Stork will migrate and apply CRDs on the target cluster iff it is migrating its corresponding CRs. But certain apps like confluent kafka, define a bunch of CRDs but don’t necessarily have a corresponding CR created. When stork migrates such an application it does not create the CRD on the target cluster for which it does not find any CR. Confluent kafka operator fails to start on the target cluster after migration since it cannot find certain CRDs.

• Stork should migrate all the CRDs under the same group for which it finds a CR even if it is for a different kind

Does this PR change a user-facing CRD or CLI?: No

Is a release note needed?:

Issue: Stork would not migrate CRDs to a target cluster if it did not find a corresponding CR on the source cluster.
User Impact: Certain Application Operators do not create all the CRs for the CRDs they define. Once stork migrates such an application, the operator fails to start the application stack since it does not find all its CRDs.
Resolution: Stork will now migrate CRDs to a target cluster which are under the same Group for which it find a CR it needs to migrate.

Does this change need to be cherry-picked to a release branch?: Yes - 2.12

[cnbu-jenkins]

Can one of the admins verify this patch?