Use lazy (old style %-format) log formatting in the new pylint config

Description of issue or feature request: Using f-strings (and all types of string formatting except %-syle) in logging messages is not lazy evaluated so linters “recommend” %-style formatting.

Should we disable the related pylint warnings and use f-strings:

logging-not-lazy
logging-format-interpolation
logging-fstring-interpolation

or adhere to the recommendation.

Current behavior: Top-level pylintrc disables logging that recommend lazy formatting globally. New api/pylintrc does not.

Expected behavior: Decide on a common approach.

[jku]

I’m proposing we use the default logging style, meaning:

• use logging-format-style=old (which is default value)
• stop disabling logging-not-lazy (note: this is done only in some experimental client branches – metadata api itself hasn’t needed this because there’s zero logging so far 😬 )

It looks a bit uglier (other string formatting is f-strings but logging is then based on %-formatting) but:

• it’s a common style
• it’s suggested by the google style guide
• it means we don’t have to think about performance when writing logging code

[joshuagl]

Proposal above makes sense to me, if it’s what’s suggested by the style guide we probably don’t even need to capture anything for this? Let’s just do what our style guide suggests.