Embed CAPI Operator reconcile inside turtles pod

[Danil-Grigorev]

What this PR does / why we need it:

Merges CAPI Operator reconcile implementation with turtles pod. Current implementation omits implementing CAPIProvider directly as a resource for the operator to reconcile.

Main reason for this is that operator holds a lot of type reflection logic, directly assigned to the existing provider types. Example, example2. This requires client wrapper to perform:

1. Conversion from CAPIProvider to *Provider resource and back to CAPIProvider without losing CAPIProvider custom fields data.
2. Populate all CAPIProvider fields which are currently set by syncer on regular operator resources, to ensure successful reconcile. Operator in addition always performs patch request on the resource, setting these ephemeral fields on the resource, breaking the no-spec-change GitOps expectation on the resource.

The solution to this is to decouple operator phases, and draw the separation for Core provider vs non-core provider. This needs to be implemented upstream first, and was attempted back in March last year in kubernetes-sigs/cluster-api-operator#475. Omitting generics introduction, it separates phases into core vs non-core.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Depends on #1510
Fixes #1397, #1415, #1413

Special notes for your reviewer:

Long run: https://github.com/rancher/turtles/actions/runs/16115602289

Checklist:

• squashed commits into logical changes
• includes documentation
• adds unit tests
• adds or updates e2e tests

Will continue with operator chart removal after some investigation. It works better and is simpler than a new flag

[anmazzotti]

Great work!