Set up Error Prone check to prevent use of native Gradle and Maven loggers

Using the native Gradle logger was probably why our deprecation messages were overwritten.

We should be careful not to make use of the native Maven or Gradle loggers. We can prevent misuse in ProjectProperties by just using consoleLogger. But it is very easy to accidentally use the native loggers in Maven mojos and Gradle tasks. Unfortunately, now I realized we had used the native loggers when printing deprecation notices.

[loosebazooka]

I think we can ask error prone to mark any use of the gradle logger or maven logger as unsafe in our codebase, just speculating though. (we would write this check)

[chanseokoh]

I tried to see how Error Prone can be configured to detect this. Looks like we have to write a custom check in Java. This seems fairly involved. May need to create another Gradle sub-project. I’ll rename this issue and add the “tech debt” label to be open.