fix(crc): recover from VMI replacement

[caxu-rh]

Summary

• Store one CRC identity Secret for each ClusterInstance. The crc-agent reuses its client and serving credentials after a VMI replacement.
• Name crc-agent Jobs and handoff Secrets with the VMI UID. The agent watches its VMI and stops before it publishes a handoff for a deleted or replaced VMI.
• Retain raw VMI handoffs. The controller rebuilds a missing published kubeconfig from the retained handoff.
• Record guest API reachability as a condition and retry /readyz checks without deleting access resources. A VMI replacement clears stale published access and starts provisioning for the replacement VMI.
• Delete crc-agent Jobs and raw handoffs by instance labels during ClusterInstance finalization.
• Add controller, resource, agent, and E2E coverage. The E2E test supplies synthetic KubeVirt, CDI, and Route APIs and removes its CRC instance before manager undeploy.

Validation

• go test ./internal/controller ./internal/resources
• go test ./test/e2e -run "^$"
• make test-e2e
• go vet ./...
• bin/golangci-lint run
• git diff --check

[exe-prow-github-app]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: caxu-rh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [caxu-rh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[caxu-rh]

/lgtm

[exe-prow-github-app]

@caxu-rh: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.