Reuse common Tiltfile approach for Cluster API Operator

[dmvolod]

What would you like to be added (User Story)?

As a developer I would like to utilize the same Tiltfile approach including deployment, redeployment and debugging for the Cluster API Operator the same common providers (addon or infrastructure)

Detailed Description

We need to deploy, redeploy and debug Cluster API Operator with the Tiltfile as it's common approach for the Cluster API
However, debug option required to do a lot of additional steps in compare with the simple Tiltfile and most of the Cluster API Starlark code should be moved to the Cluster API operator and maintaned.
In this case, it would be nice to reuse the common steps including in the Cluster API Tiltfile, but not require always_enable_providers = ["core"] to be enabled.
For this feature, I would like to implement an option for tilt-settings.yaml that allows not to always enable the Core Provider.

Any ideas will be appreciated.

Anything else you would like to add?

First part of the task is implementing in kubernetes-sigs/cluster-api-operator#726

Will provide fix, if this approach will be suitable.

Label(s) to be applied

/kind feature
/area devtools

[chrischdi]

/triage accepted
/priority important-longterm

It is fine to add a knob to disable the core provider, as long as we keep the default as it is today.

[dmvolod]

/assign