bring back stderr and remove extraneous scaffolding and taunting stderr spam

this pull request does two things

1. eliminates the source of a stderr message that always shows up about logging.
It appears to have been coming from our main class where someone shoved in what
looks like a reimplementation of log4j standard init but with automatic filesystem
searching. Adding the etc directory to our classpath accomplishes the same thing.

2. brings back stderr functionality without having to use System.err.println. This
is particularly important since spawn has all this otherwise useless stderr support.
The current setup is that logging messages that are ERROR level go to stderr and all
others go to stdout.

between the two of these, I would like to see stderr being non-empty as a more
notable event. Someday being able to alert on it and have that be reasonable
would be nice.