Update apport reporting

[Chris-Peterson444]

Some name and file location changes to be consistent with the (to be upload) updated subiquity hook in apport.

The only source of the traceback - if any - is the one in memory that we grab and manually attach to the report. We also need to explicitly write out the traceback information when we crash, otherwise a call to ubuntu-bug or similar won't be able to pick it up.

[Chris-Peterson444]

The not-yet proposed subiquity hook in apport:
https://git.launchpad.net/~cpete/ubuntu/+source/apport/commit/?id=c64966a06cf0a29f8ade0636d3ead77f817ac24a

[Chris-Peterson444]

Here are some example crash reports for these changes:

Subiquity's geneated crash report: https://bugs.qastaging.launchpad.net/subiquity/+bug/1743387
Apport's generated crash report: https://bugs.qastaging.launchpad.net/subiquity/+bug/1743388

Since these links will be dead after some time, here are the corresponding crash files (renamed to .log so github will let me post them):
apport-crash.log
subiquity-crash.log

[Chris-Peterson444]

In preparing this I've come to realize that while apport-cli states that using the -c flag will only upload the crash file, it appears to also run the package hook, if found, and overwrite any of the fields already in the report. This also means things like InstallerJournal and SystemJournal may both be present in the report. I will update the hook to only include SystemJournal if InstallerJournal is not found.

This is mostly an issue for the server installer, where a crash requires the user to manually report the bug using ubuntu-bug or apport-cli. Although I will need to confirm if this is the case when running ubuntu-desktop-installer.

An additional note is that given the current permissions of /var/installer/log/ a user is required to run ubuntu-bug or apport-cli with sudo.