sending "A newer version of RITA is available!" message to stdout instead of stderr makes the resulting CSV unparseable

It's helpful to know that a newer version is available, but tacking that on to the end of the CSV output broke our automated workflow that has logstash parse the CSVs and ship into ELK.

Perhaps this output could go to stderr instead of stdout?