[Flare] Collect osquery and launcher coredumps

[RebeccaMahany]

Occasionally we see segfaults from osquery (for example, #1773), and these are tough to debug with the information we currently. We have logs from osquery, but we cannot always correlate them with the segfault, and it's a bit tough to sift through with how noisy all the launcher logs are.

What was really helpful with the last segfault issue was collecting coredumps from affected devices. We should start to add these to flares so that we can collect them automatically.

We can use abrt-cli list or coredumpctl list to see if there are any coredump files. We should include in the flare any coredumps that come from Kolide's osquery or launcher installations -- these files may live in /var/spool/abrt (Fedora) or /var/crash (Ubuntu) or other locations depending on Linux distro. We can also collect the outputs of coredumpctl info osqueryd and coredumpctl dump osqueryd.

[directionless]

probably for both launcher and osqueryd