Add responseCauseSanitizer to LoggingDecoratorBuilder

[trustin]

Motivation:

A user wants to sanitize the stack trace of RequestLog.responseCause()
or avoid logging the stack trace completely.

Modifications:

• Added LoggingDecoratorBuilder.responseCauseSanitizer()and applied the specifiedFunction` to the response cause.
• Widened the type parameters of sanitizer functions.
• Miscellaneous:
  • Fixed a bug where a response content sanitizer is applied on request
    content on a certain case.
  • Added contentSanitizer() and headersSanitizer() shortcut methods.
  • Javadoc clean-up

Result:

• A user can sanitize/drop the stack trace of RequestLog.responseCause().
• Request content is always sanitized with an intended sanitizer.
• More shortcut methods in LoggingClientBuilder and LoggingServiceBuilder.

[trustin]

@anuraaga I found we do not log RequestLog.requestCause(), so I did not add requestCauseSanitizer(). Do you think we need to add requestCauseSanitizer() and start to log a request cause? I'm curious why we did not so far. Any clues?

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@ff46158). Click here to learn what that means.
The diff coverage is 79.16%.

@@            Coverage Diff            @@
##             master    #1594   +/-   ##
=========================================
  Coverage          ?   72.82%           
  Complexity        ?     7574           
=========================================
  Files             ?      699           
  Lines             ?    30459           
  Branches          ?     3712           
=========================================
  Hits              ?    22182           
  Misses            ?     6369           
  Partials          ?     1908

Impacted Files	Coverage Δ	Complexity Δ
...corp/armeria/common/logging/DefaultRequestLog.java	80.09% <ø> (ø)	144 <0> (?)
...om/linecorp/armeria/common/logging/RequestLog.java	25.71% <ø> (ø)	8 <0> (?)
...p/armeria/client/logging/LoggingClientBuilder.java	100% <100%> (ø)	3 <0> (?)
.../armeria/server/logging/LoggingServiceBuilder.java	100% <100%> (ø)	3 <0> (?)
...rp/armeria/internal/logging/LoggingDecorators.java	100% <100%> (ø)	8 <6> (?)
...inecorp/armeria/server/logging/LoggingService.java	65.62% <66.66%> (ø)	6 <0> (?)
...linecorp/armeria/client/logging/LoggingClient.java	62.5% <66.66%> (ø)	6 <0> (?)
...rmeria/common/logging/LoggingDecoratorBuilder.java	63.63% <73.33%> (ø)	21 <7> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff46158...ee21f27. Read the comment docs.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@ff46158). Click here to learn what that means.
The diff coverage is 79.16%.

@@            Coverage Diff            @@
##             master    #1594   +/-   ##
=========================================
  Coverage          ?   72.82%           
  Complexity        ?     7574           
=========================================
  Files             ?      699           
  Lines             ?    30459           
  Branches          ?     3712           
=========================================
  Hits              ?    22182           
  Misses            ?     6369           
  Partials          ?     1908

Impacted Files	Coverage Δ	Complexity Δ
...corp/armeria/common/logging/DefaultRequestLog.java	80.09% <ø> (ø)	144 <0> (?)
...om/linecorp/armeria/common/logging/RequestLog.java	25.71% <ø> (ø)	8 <0> (?)
...p/armeria/client/logging/LoggingClientBuilder.java	100% <100%> (ø)	3 <0> (?)
.../armeria/server/logging/LoggingServiceBuilder.java	100% <100%> (ø)	3 <0> (?)
...rp/armeria/internal/logging/LoggingDecorators.java	100% <100%> (ø)	8 <6> (?)
...inecorp/armeria/server/logging/LoggingService.java	65.62% <66.66%> (ø)	6 <0> (?)
...linecorp/armeria/client/logging/LoggingClient.java	62.5% <66.66%> (ø)	6 <0> (?)
...rmeria/common/logging/LoggingDecoratorBuilder.java	63.63% <73.33%> (ø)	21 <7> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff46158...ee21f27. Read the comment docs.

[anuraaga]

Hmm - I don't know if I've ever thought of the existence of request cause. Any request exception would probably be logged in the response itself so it seems likely to double-log if the request cause was logged.

[trustin]

Yeah. That's probably why. Let me keep it this way then. Thanks for a reply.

[trustin]

Thanks for reviewing :-)