lalpulsar_compareSFTs is silent on exceeded tolerance

@karl-wette while testing, I noticed that when comparison tolerance is exceeded, this tool return a 1 exit code as expected, but does not print any message. Meaning that if one just runs it on the command line without further checks on the return code and expects silence==golden, one will miss cases with relevant difference.

I can do a one-line MR to improve this, but wanted to first check with you (and on the next CW call) if anyone remembers if this was implemented that way on purpose, e.g. a traditional use-case where silence is required.