Test changes to show we can have funkily named fields.
Issue #1170: Change error handling in CeylonCompileTool and Main.

Revise CompilerErrorException, CompilerBugException and SystemErrorException so they don't use @NonFatal

CeylonEnter & CeylonLog: Account for ceylon codegen errors separately from analysis errors, so we can properly distinguish between analysis errors, bugs in our codegen and bugs in later javac phases. We need to do this to properly distinguish typechecker error cases from compiler bug cases. Do this by using and keeping a count of different message keys in CeylonLog.

Main: Use an ExitState class to save adding lots of fields to Main and to centralize the logic for figuring how when something is an comtpile time error or a bug.
Issue #1170: CeylonTool: Revise error handling now that @NonFatal has been removed and
we can use the ToolError and FatalToolError classes directly to figure out a sensible error message.
Issue #1170: langtools compiler.properties: New message keys.
Issue #1170: When we handle an uncaught exception during codegen, log it via the javac log, rather than std err.
Issue #1170: CodegenUtil: Add methods to get a compiler annotation's value.
Issue #1170: CeylonTransformer when using the CeylonVisitor make sure we actually visit the Tree.CompilationUnit, in particular so we can process compiler annotations on the compilation unit.
Issue #1170: CeylonVisitor: Add visit(Tree.CompilationUnit), handling the @die annotation
Issue #1170: Better handling of unknown compiler annotations.
Issue #1170: test: ErrorCollector: Fix for the new message keys.
Issue #1170: When reporting that there were parser or lexer failures, use Log.printErrLines() (which doesn't increment the error count), to avoid reporting a number of errors that is one more than there actually is
Issue #1170: Fixup test now that a parser failing is no longer itself an error.
Issue #1170: Add support for an @erroneous compiler annotation which produces a JCErroneous in the javac tree, so that we can test that we handle this error case correctly.
Issue #1170: test: Add some test cases various kinds of compiler error and bug cases.
tests: Use metamodel refs for see() annotations.
Issue #1170: Not sure: Better error handling?