feat: clearer error messages when not using block

[bittermandel]

When using keto status to check server health, it is not clear why the server might not be healthy. For example, if accessing the server through an insecure connection, the command would log NOT_SERVING and return 0, rather than Unable to get a check response: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: EOF with exit status 255.

This PR improves this slightly by logging the actual error that the gRPC client returns rather than wrapping it in a NOT_SERVING error. It also makes sure that the status command respects block and doesn't add a timeout by default, as otherwise the error will always be "Context deadline exceeded".

I am very happy to chat about how I can add sufficient docs and tests for these changes!

PS: The quality of this PR can most likely be improved and I'm happy to take feedback on how to do that.

Related issue(s)

Checklist

• I have read the contributing guidelines.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I am following the
  contributing code guidelines.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security vulnerability, I
  confirm that I got the approval (please contact
  security@ory.sh) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added or changed the documentation.

[CLAassistant]

All committers have signed the CLA.

[hperl]

LGTM! Thank you for your contribution!