Add harpoonctl agent events subcommand

It's totally normal that (n-1) agents in a cluster would hit this code path. Making it unconditionally a warning gives the user the wrong signal, I think. Maybe some inspiration is possible [from the log command](https://github.com/soundcloud/harpoon/blob/master/harpoonctl/agent/log.go#L63-70).