Summary:
the operator's monitor is responsible for:
1. watching the K8s API for tracking the latest pod statuses. we keep a version of this in memory since the # of vizier pods is small. the retry watcher code is mostly borrowed from the vizier metadata's retry watcher code.
2. periodically pinging the statusz endpoints of the vizier pods to determine the latest state. for now, this logic is very simple and we only look at whether the cloudConnector can run basic queries (this is the status quo). once the entire pipeline is more built out, we can make this even smarter.

Test Plan: skaffold deployed vizier and operator. played around with cloudconn status to make sure the CRD status gets updated to reflect its new state.

Reviewers: vihang, nserrino, zasgar

Reviewed By: vihang

JIRA Issues: PP-2875

Differential Revision: https://phab.corp.pixielabs.ai/D9466

GitOrigin-RevId: 8482820e17982959bb47615068bfdd98a6ddbb0b