Set status.cond when cluster secret not found

[ChunyiLyu]

Requested in rabbitmq/cluster-operator#1375

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Note to contributors: remember to re-generate client set if there are any API changes

Summary Of Changes

Previously error was only logger, with this commit status.condition log and event are all updated.

Before:

Spec:
  Ack Mode:  on-confirm
  Name:      origin
  Rabbitmq Cluster Reference:
    Connection Secret:
      Name:  secret-that-doesnt-exist
  Uri Secret:
    Name:  federation-uri
  Vhost:   downstream
Events:    <none>

With this change:

Spec:
  Ack Mode:  on-confirm
  Name:      origin
  Rabbitmq Cluster Reference:
    Connection Secret:
      Name:  secret-that-doesnt-exist
  Uri Secret:
    Name:  federation-uri
  Vhost:   downstream
Status:
  Conditions:
    Last Transition Time:  2023-06-09T12:19:49Z
    Message:               failed to retrieve cluster from reference: Secret "secret-that-doesnt-exist" not found
    Reason:                FailedCreateOrUpdate
    Status:                False
    Type:                  Ready
Events:
  Type     Reason                Age                   From                   Message
  ----     ------                ----                  ----                   -------
  Warning  FailedCreateOrUpdate  65s (x15 over 2m27s)  federation-controller  failed to retrieve cluster from reference: Secret "secret-that-doesnt-exist" not found

Additional Context

[michaelklishin]

Just FTR, I wanted to suggest using a "type error" here but apparently there only "normal" and "warning" to choose from in the API :)