`argo cron` should report when CronWorkflow names exceed the length limit

# Summary

The `argo cron` command faithfully lists CronWorkflows, even ones that are rendered invalid due to the name exceeding the 52-character limit.

The workflow controller does log the issue. But `argo cron` gives the impression that nothing is wrong.

# Use Cases

My team would benefit from this when a dev (who is unfamiliar with the workflow controller and its logs) deploys a CronWorkflow and then uses `argo cron` to maintain that CronWorkflow.

---

**Message from the maintainers**:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Start at the `argo cron` command entry point and reproduce the behavior with a CronWorkflow whose name exceeds the 52-character limit. Compare the command's output with the workflow controller's logged validation issue; done means `argo cron` clearly reports that the CronWorkflow is invalid instead of presenting it as healthy.

Written by the indexing model from the issue text.