[BUG] Start controller-runtime manager in single binary even if webhook is disabled

[hamersaw]

Describe the bug

Currently the single binary only starts the controller-runtime manager if the propeller webhook is enabled. This means in the case where webhook is disabled propeller is unable to be notified of k8s resource updates and in turn has much worse performance in workflow evaluations because it only evaluates workflows using the reeval duration.

Expected behavior

The controller-runtime manager should be started in single binary even if the propeller webhook is disabled.

Additional context to reproduce

Disable the propeller webhook in single binary using the disableWebhook configuration option and start single binary.

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes