Use the MI image workflow for cloud integrations

[Dilhasha]

New cloud MI integrations currently select mi-buildpack-builder. Select mi-image-builder for MI API services, scheduled tasks, manual jobs, webhooks and event handlers so they use the workflow that packages CARs into official WSO2 MI images.

This changes only the five MI entries in the cloud component-creation mapping. Ballerina mappings are unchanged.

Validation: the cloud UI production build and all five existing component API tests passed. The rebuilt local console bundle contains the new workflow name, and existing local MI components were migrated separately.

Deploy after mi-image-builder is installed and allowed by the relevant component types. Existing components retain their saved workflow reference until migrated.

Companion PRs:

• Deployment workflow ( Local setup) : https://github.com/itsvishwa/wso2cloud-deployment/pull/2
• Organization defaults: https://github.com/wso2-enterprise/wso2cloud/pull/1492
• Console selection: Use the MI image workflow for cloud integrations #976

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: fce22f6d-0004-4f7f-b40a-55c51d17bc60

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}