[Feature]: Cluster operators can deploy and scale controllers independently

[pbusko]

Blockers/Dependencies

none

Background

As a Cluster operator
I want to be able to run the job-task-runner, kpack-image-builder and statefulset-runner controllers independently from the Korifi Controller (standalone Deployment's)
So that I can scale (and monitor) them based on the actual load. With this approach we eliminate a single point of failure, as well as we also make sure that the RBAC entities (ServiceAccounts) assigned to controllers have a minimal rights (instead of a single ServiceAccount for all controllers).

Acceptance Criteria

The job-task-runner, kpack-image-builder and statefulset-runner controllers are no longer part of the Korifi Controller codebase and they are running as a separate configurable deployments.

Dev Notes

On the Helm Chart side, the changes should be backward compatible. Properties like

korifi/helm/korifi/values.yaml

Lines 112 to 113 in f9b24a3

	statefulsetRunner:
	include: true

should materialize actual deployment, instead of adding a flag to the Korifi Controller config. Additional input values (like resources/limits configuration should be optional with sane defaults).