Fix crash reporter to capture logs from main process
Since we can't reliably attach arbitrarily large data to the intent starting the crash reporter (and it would otherwise only grab logs from its own process), this MR introduces encryption and decryption for logs that is used to store them on disk, so the crash reporter process can read and decrypt them from there.
Test instructions:
- use developer build of briar
- go to settings, open feedback, scroll to App log and verify that it contains the real app log
- in settings, crash the app with the developer crash option, open the crash report data, scroll to app log and verify that it contains the real log
- recent briar versions without this fix only shows the app log of the crash reporter which always looks the same and doesn't contain the real log we need for bug diagnosis
Closes #1917 (closed)
Edited by Torsten Grote