When libunwind fails to resolve a particular frame during outputting stack traces, we will output a message to the logs.

This happens quite often currently, due to SERVER-98741's explanation that libunwind currently fails trying to unwind through the VDSO, which is often used.

Often, those who are triaging failures see this message and assume the rest of the stacktrace is missing; the stacktrace is present, though the frame is missing.

This ticket is to modify that message to be clearer, so that TSEs and engineers looking at stacktraces don't go down a rabbit hole assuming more information is missing than what actually is.

There is an unmerged pull request in the libunwind repo to fix this behavior.