WHAT

For MGDSTRM-8813 Strimzi team have a 0.4.0 fix for assigned (https://github.com/strimzi/strimzi-canary/pull/191) - which i think seems reasonable for an upstream position. For managed kafka, we can't wait 0.4.0 as the defect affects 6 broker kafkas.

We need to backport the fix and make a canary release.

WHY

Prevents canary topic partitions being improperly assigned.

HOW

1. Backport the PR to https://gitlab.cee.redhat.com/mk-ci-cd/strimzi-canary/-/tree/mk-release-0.3.x . Be sure to reference the Jira number in the commit as this is important to the managed service piplelines.
2. Create a release tag mk-release-0.3.0-2
3. Run 
   https://jenkins-cpaas-rhosak.apps.cpaas-poc.r6c9.p1.openshiftapps.com/job/main/job/mk/job/poll-upstream-sources/
    
   That will trigger CPaaS to automate the update to the build config and trigger a scratch build. Once that's all completed (in a couple hours probably), the permanent build can be trigger in Jenkins.
4. Test the candidate rhosak index build in OSD development using kas-installer (by overridding https://github.com/bf2fc6cc711aee1a0c2a/kas-installer/blob/c8bbfce5cba5274e824eb795b73f50057b4f68f2/kas-installer-defaults.env#L137)

DONE

Include the following where applicable:

• Tested rhosak index build ready for release.