changed my mind about explicitly calls to error()

Before, this would always cause a report, even if the response code indicated the error was probably a client problem.
However, because
* the logging appenders call error(),
* the EJB container seems to log exceptions thrown from any EJB (even client-ish exceptions)
* I’m not sure how to keep it from doing that
I’m going to reverse this behavior.
make sure the error message isn’t too crazy long

Currently, if the error message comes from a log message with a stack trace, it can be ridiculously large.
change how user/client errors are handled

* they are now enqueued, but
* NativeErrbitReporter doesn’t send them (Errbit doesn’t nicely ignore/silence client errors)

Potentially, other reporters might have this capability, so it makes sense to make user-error-suppression the responsibility of the reporter, not the recorder.
clean imports
Merge pull request #2 from CruGlobal/log-trigger-modifications

Log trigger modifications