feat(native): add crashpad-wait-for-upload option (#13117)

* add crashpad-wait-for-upload option

* edit backend tradeoffs for crashpad

* apply suggestion

Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>

---------

Co-authored-by: Mischan Toosarani-Hausberger <[email protected]>

Author: JoshuaMoelans

docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

@@ -32,12 +32,13 @@ Sentry decided on `crashpad` as the default on all platforms because there are a
 * you cannot package or deploy an additional executable (the `crashpad_handler`)
 * you cannot allow a secondary process to connect via `ptrace` to your application (AWS Lambda, Flatpak-, Snap-Sandboxes)
 * IPC between your process and the `crashpad_handler` is inhibited by security settings or not available in your deployment target
-* your deployment scenario cannot wait for the `crashpad_handler` to finish its work before a shutdown-after-crash (systemd, Docker)
 * you want to distribute your application via the macOS App Store
 * you want to define crash hooks on macOS because there, error handling happens entirely in the `crashpad_handler`, whereas on Linux and Windows, at least the initial handling happens in your process, after which `crashpad_handler` takes over and snapshots the process to send a crash report
 
 In the above cases, if you cannot loosen the requirements of your environment, you have to choose an in-process backend (meaning either `breakpad` or `inproc`).
 
+When your deployment scenario should wait for the `crashpad_handler` to finish its work before a shutdown-after-crash (systemd, Docker), you can enable the option [`crashpad_wait_for_upload`](/platforms/native/configuration/options/#crashpad-wait-for-upload) to delay application shutdown until the upload of the crash report is completed.
+
 ### How do I decide between `breakpad` or `inproc`?
 
 Both backends are comparable in how they differ from `crashpad`. However, there are also considerable differences between the two:

docs/platforms/native/common/configuration/options.mdx

@@ -60,6 +60,12 @@ This variable controls the total amount of breadcrumbs that should be captured.
 
 </ConfigKey>
 
+<ConfigKey name="crashpad-wait-for-upload">
+
+Whether Crashpad should delay application shutdown until the upload of the crash report in the `crashpad_handler` is complete. This is useful for deployment in `Docker` or `systemd`, where the life cycle of additional processes is bound by the application life cycle.
+
+</ConfigKey>
+
 ## Hooks
 
 These options can be used to hook the SDK in various ways to customize the reporting of events.