Otherwise the backtrace area looks a bit broken, surrounded by
all of the empty space

GIT_SILENT

was not connected to anything and consequently did nothing

GIT_SILENT

snuck by accident when merging

usefulness changes as the first lines trickle in, leading to the status
item saying things are useless when indeed it's not done loading yet.

BUG: 453538

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

lest distros miss them

:? returns the var if defined or errors if undefined. so we need to
assign the output back into the var, otherwise we'd try to implicitly
run the content of the variable (and that is a dir so it makes zero
sense - plus is not what is intended here anyway)

the old qwidget UI sticks around for safer mode (for now) just in case
the qml view goes belly up.

BUG: 443781

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

this is still a bit crap because you can't scroll horizontally because
that gesture is already used for switching pages. so. I don't know, but
this is certainly better than doing text selection on mobile 🤷

the user socket also needs to be enabled otherwise the processor has
nobody to talk to

apparently 0-123-0 is the escaped variant (%i) whereas I thought it is
the unescaped variant (%I). since we want the version with hyphens (so
we can use them in the filtering tech) use %i here.

unit names always have a type suffix, in this case the instance is the
prefix (so we can startwith filter on) meaning we need to add the suffix
manually for the builtin matching tech

it indeed serves no practical purpose and is actually counterproductive
for the coredump-gui

3 numbers but 2 hyphens. one can see where my brain took the wrong turn
;)

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

from testing it seems this works fine now. no reason to disable as far
as I can tell

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

it is a GUI for coredumpctl - duh.

There are two main motivations behind this

- provide more user friendly access to coredumps (and thus allow more
crashes to be reported to the relevant authors)
- it is the foundation for plans to aggregate crashes. right now
multiple crashes result in multiple drkonqis but realistically we could
just feed them all into a singular UI. coredump-gui kind of gets that
started as the UI bits actually aren't coredump related at all so we can
iterate from here

this also contains some rejiggering of the existing coredump code to
facilitate more code sharing through a new internal static library.

architecture-wise the gui is super simple. there's a central Patient
concept which "abstracts" a crashed application. Patients are managed by
a PatientModel (which is really just a generic QObject model) and get
fed into that model by the existing coredumpwatcher tech. the qml bits
then simply view the model/patients. without coredumpd in the picture
the Patients would be synthesized through other means as yet to be
invented.

```
[General]
IncludeAll=true
```

When in IncludeAll mode we catch all crashes, not just ours. This is
critically important on mobile where we are in control of the entire
stack more or less and want to know when networkmanager or whatever
crashes

also improve the test linkage while at it

instead of building bugzillalib twice we will simply use it from the
static ephemeral lib. saves time and also means the new drkonqi link
dependency is met

- comprehensively cover notify/constant requirement
- fully qualify enums in invokables