Remove ready field from status

The usage of such a field is considered deprecated, conditions
should be used instead.

If there is a use-case that is not covered by conditions only
we can always reconsider adding an extra field to the status.

See the k8s guidelines for more details on the deprecation:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

deploy/crds/onepassword.com_onepassworditems_crd.yaml

@@ -63,9 +63,6 @@ spec:
                   - type
                   type: object
                 type: array
-              ready:
-                description: True when the Kubernetes secret is ready for use.
-                type: boolean
             required:
             - conditions
             type: object