Use Sentry logs to log stacktrace for Debug/Dev builds

[mujacica]

With 7aa553c we removed an option to print the stacktrace during OnCrash handling since that was causing secondary Sentry crashes whenever there was any kind of memory-allocator/stack corruption happening.

Having this feature re-integrated, now with Sentry logs - and on all platforms, would be helpful for Debug/Development builds (that don't have symbols uploaded).

We should:

• Add an option to enable OnCrash logging (with note about not-prod safety)
• Try to cover all platforms (not only Windows)

[linear]

UNREAL-109

[tustanivsky]

While stack trace logging was re-integrated for Windows and Xbox in #1170 and #1177 these messages are currently not forwarded to Sentry logs because in sentry-native they are flushed before the on_crash callback is invoked.

[mujacica]

@tustanivsky can we create a follow-up ticket in sentry-native to address this?

[tustanivsky]

Sure, here's the corresponding issue for Native SDK - getsentry/sentry-native#1473

[tustanivsky]

Piping messages that were emitted during crash handling to Sentry logs was enabled in Native SDK via getsentry/sentry-native#1474 and is available staring from version 0.12.3 (bumped for Unreal in #1187).

Note: messages logged during Unreal’s custom crash handling are uploaded to Sentry after restarting the app. This is expected behavior since flushing the logs in sentry-native only writes the corresponding envelope to disk to avoid transport queuing during crash (see ref).