Use Java Util Logging for debug-level messages so that we can turn it down later.
Configure the JUL Loggers to only print out the level name.
Adjust logging levels so that fewer messages are issued.
Use logback and sl4j for logging because I kept getting ClassNotFoundExceptions when using Java Util Logging.
Fix problem with logback.xml that was causing a bunch of boilerplate info- and warning-level messages to be printed when the program starts up.
Added a -debug flag to increase the amount of logging by the GraderTools application.
Broke up a huge main method into smaller methods to make this code easier to work with.  Also got rid of the IntelliJ warnings.
Use method references to clean up the amount of code it takes to configure the Student object created by the Survey program.
More refactoring to make the main method smaller.
To address issue #50, add the answers to the "What would you like to learn?" and "What else would you like to tell me?" question as "notes" on the Student created by the Survey program.
Log a message stating that the Survey email was sent.  Otherwise, the student doesn't know what happens when the program finishes.
To address issue #50, any notes about a Student are printed out when the student's survey results are imported into the grade book.
Merge pull request #94 from DavidWhitlock/issue-50-print-survey-comments

Address issue #50 by capturing the answers to the survey questions, "What do you hope to learn in CS410J" and "What else would you like to tell me?" as "notes" on the Student created by the Survey program. The "notes" are then printed by the program that imports Students into the grade book. Along the way, I introduced better logging into the code that downloads emails (using logback) and refactored the Submit program to be more readable.