Allow exception logging to be customizable for activity failures

[markcho]

Is your feature request related to a problem? Please describe.
We have some use cases where we leverage ApplicationFailure.nonRetryableError for some failures that we expect to happen from an activity.

In these cases, we don’t want these failures to be logged as error. Since we also use a service like Sentry for exception monitoring in our prod services, these expected activity failures will pollute the log and would prefer to only log unexpected failures.

Describe the solution you'd like
Some approach to customize activity failure error logging.
Maxim's proposal was to create a logger per error type as described in here: https://community.temporal.io/t/java-sdk-allow-exception-logging-to-be-customizable-for-activity-failures/2887

Describe alternatives you've considered
An alternative I've considered was to never let expected failures to cause an ApplicationFailure but to model this into a return type.

[mfateev]

My current view is that we should add a flag (or separate method for creation) to allow creating an ApplicationFailure that is not logged. All other failures are logged.

[Quinn-With-Two-Ns]

We should also cover the generation of activity exceptions in the ActivityTaskExecutor when executing the activity. Specifically for data converter exceptions.

[inspell]

I also need to customize the logging configuration. I use activities for polling, and I throw exceptions from the activity to retry the poll. This currently pollutes the logs. Is there any update on this?

[darshan-au]

+1 on this
We use activities for polling and the constant failures pollute the logs a lot

[inspell]

Hello! I am also tracking this issue. My initial "want" was this: temporalio/sdk-go#78
Which is already implemented in the Go SDK. Will this also be available in the Java SDK? It appears to be exactly what this ticket describes.

EDIT: It looks like it is already available: #2485