feat(drift-detection): add periodic drift detection to all controllers

[digiserg]

Summary

• Adds DriftCheckInterval = 5 * time.Minute constant to the common package
• Adds a checkDrift helper method to each of the 14 CRD controllers
• When a resource is already synced (Ready=True, ObservedGeneration matches, synced ID non-empty), the controller calls checkDrift to verify the resource still exists externally in AxonOps before short-circuiting
• If drift is detected (resource was deleted externally), sets DriftDetected condition, clears the synced ID, and falls through to recreate
• If the drift-check API call fails, sets DriftCheckFailed condition and requeues after the drift interval

Design notes

• Controllers that resolve apiClient before the idempotency guard (most): checkDrift takes apiClient as a param
• Controllers that resolve apiClient after the idempotency guard (AlertEndpoint, AlertRoute): checkDrift resolves its own client internally
• Singleton resources without IDs (AdaptiveRepair, DashboardTemplate, CommitlogArchive): drift detected by settings comparison or empty-list check
• Kafka controllers (Topic, ACL, Connector): no drift detection — no List/Get API methods available
• Extracted applyRoute helper in AlertRoute to keep Reconcile cyclomatic complexity ≤ 30

Test plan

• make lint passes with 0 issues
• make test passes across all packages
• LogCollector idempotency test updated: mock server is stateful, asserts 1 drift-check GET and 0 extra PUTs
• Manually verify drift detection by creating a resource, deleting it in AxonOps UI, and confirming the operator recreates it within 5 minutes

Closes #94