[PDS-119625] Log the Exception, not UnsafeArg.of(exceptionMessage)

[jeremyk-91]

Goals (and why):

• See PDS-119625
• This made debugging somewhat annoying: you lose the failure type stack trace (and in the event t is actually Safe, you lose all information!)

Implementation Description (bullets):

• Log the exception, not UnsafeArg.of(exceptionMessage).

Testing (What was existing testing like? What have you done to improve it?): none

Concerns (what feedback would you like?):

• This may increase logging payloads. It won't pollute the logs from a user PoV so this would primarily be in terms of logging infra. I think the cost is reasonable.

Where should we start reviewing?: CCPC

Priority (whenever / two weeks / yesterday): this week

[changelog-app]

Generate changelog in changelog/@unreleased

Type

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

Description

The type and stack trace of Exceptions when talking to Cassandra are now logged (and in the case of Safe exceptions, the exception message will also be available). Previously, only the exception message was logged, and this was always Unsafe.

Check the box to generate changelog(s)

• Generate changelog entry