Ignore non-literal arg names in LogsafeArgName

[pkoenig10]

Before this PR

The LogsafeArgName check would fail if using a compile time constant identifier (static final variables) for args names.

This fails with the following exception:

java.lang.AssertionError: An unhandled exception was thrown by the Error Prone static analysis plugin.
     Please report this at https://github.com/google/error-prone/issues/new and include the following:
  
     error-prone version: 2.4.0
     BugPattern: LogsafeArgName
     Stack Trace:
     java.lang.ClassCastException: class com.sun.tools.javac.tree.JCTree$JCIdent cannot be cast to class com.sun.tools.javac.tree.JCTree$JCLiteral (com.sun.tools.javac.tree.JCTree$JCIdent and com.sun.tools.javac.tree.JCTree$JCLiteral are in module jdk.compiler of loader 'app')
  	at com.palantir.baseline.errorprone.LogsafeArgName.matchMethodInvocation(LogsafeArgName.java:77)
  	at com.google.errorprone.scanner.ErrorProneScanner.processMatchers(ErrorProneScanner.java:451)

After this PR

The LogsafeArgName ignores arg names that are not literals.

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

The LogsafeArgName now ignores arg names that are not literals.

Check the box to generate changelog(s)

• Generate changelog entry

[carterkozak]

nit: we might as well combine these two conditional expressions.

[pkoenig10]

We can just get rid of the compile time constant matcher, right? All literals are compile time constants.

[carterkozak]

Yep, you're right

[svc-autorelease]

Released 3.36.1