Add both checks to ovn-controller on ovn-operator that currently doesn't have any of those checks.

Liveness for controller is probably just "pid up"

Readiness may be something more elaborate. In ovn-k has some readiness logic that validates sb and ovsdb and ofproto connections here [1]

[1] https://github.com/ovn-org/ovn-kubernetes/blob/c54dc7b0dda70baf627e9bf95cb7e19028929c62/go-controller/cmd/ovn-kube-util/app/readiness-probe.go#L15 

NOTE: this Jira is for ovn-operator only; EDPM readiness / liveness checks, if any, should be tracked separately.