After previous discussion, put eye-catcher 'SCRIPT READY' messages to console rather than log as warning

The problem with logging at warn is that these aren't actually warnings, and so are false positives to scripts that monitor for problems.
Ideally, log4net would have a separate "status" logging level, but currently we will compromise by putting them to console, as they are user-oriented