fix: report Available condition in version resolution controller

[cristianoveiga]

Summary

• The VRC only reported Applied condition after resolving a version, but the CLS backend aggregates Available conditions to compute cluster-level Ready status
• Without Available, the cluster stays at PartiallyReady (1 of 2 controllers) even when the HostedCluster is fully healthy
• This caused the e2e pipeline to time out waiting for Ready=True

Changes

• Add SetAvailableTrue("VersionResolved", ...) on successful version resolution
• Add SetAvailableFalse("ResolutionFailed", ...) on failed version resolution

Evidence

Backend aggregation (status_aggregator.go:89) only counts controllers with Available: True:

WHERE condition->>'type' = 'Available' AND condition->>'status' = 'True'

Pipeline failure showed cls-hypershift-client reporting Available: True but cls-version-resolution-controller only reporting Applied: True, resulting in "1 of 2 controllers ready".

Test plan

• go build ./... passes
• go test ./... passes
• Deploy to integration and verify cluster reaches Ready: True (2/2 controllers)
• E2e pipeline passes

🤖 Generated with Claude Code

[apahim]

/lgtm