chore(logging): add access-token request debug logging

[Erik Schmidt (eschmidtfds)]

Description

• adds logging of the access-token request and its response for troubleshooting purposes
• chose 'trace' as the log level in an attempt to lower the risk of this being enabled in production
• chose to log the data in one line instead of multiple lines, to avoid issues with logging tools that only support one line per log message, however the response is logged as-is.
• Note: removed sl4fj-simple from the dependencies
  • on the one hand it clashed with the logback test-dependency I use for intercepting logs during tests
    (sl4fj complaining about multiple bindings being available)
  • on the other hand we also should not ship with a binding at all and instead leave that choice to the user.
  • One caveat now is that SLF4J will print this warning on stderr if a user adds our lib without also adding a slf4j-binding:

    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
    SLF4J: Defaulting to no-operation (NOP) logger implementation
    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
    

  • why logback over slf4j-simple: had an easier time configuring logback to suppress logs other than the one i need during a test run

Links

Testing

Checklist

Ensure the following things have been met before requesting a review:

• Follows all project developer guide and coding standards.
• Tests have been written for the change, when applicable.
• Confidential information (credentials, auth tokens, etc...) is not included.

[CLAassistant]

All committers have signed the CLA.