Including corelens & drgn versions in reports

[brenns10]

There are two related issues fixed here:

1. The useful messages that give the debuginfo type and the runtime are only printed in "report mode", which is when -o is used. LKCE does not use report mode, so its reports don't have that information, which is a shame. To fix this, add a "corelens" section to the stdout output whenever more than one module is run. This ensures that the common case of corelens VMCORE -M one_module doesn't get a bunch of extra output that won't be useful for most people.
2. Some useful info was missing in this output - the drgn-tools & drgn versions. So add that in.

To make the versions even more useful, I've updated the packaging scripts so that the version string reported by corelens is (nearly) identical to the RPM version, if it was installed via the RPM. That can help differentiate between supported & unsupported installations (e.g. running from git or from source).

I'm avoiding adding options like --verbose or --quiet here because the logic is already complicated enough. I'd like to avoid custom flags to add or remove specific kinds of output. Hopefully each of the above modes is intuitive enough that people don't really need to think about it - the output just makes sense.

To test this, I've verified that the output for each of the three possible cases (described in the code) and I've also built the RPMs on OL9 and installed. Here's what it looks like for a silly (small) output on my laptop where we're running multiple modules to stdout:

$ corelens /proc/kcore -M ls / -c -M ls /home/stepbren -c
warning: Running corelens against a live system.
         Data may be inconsistent, or corelens may crash.

====== MODULE ls ======
/:
        23 positive, 339 negative dentries

====== MODULE ls ======
/home/stepbren:
        115 positive, 375 negative dentries

====== corelens ======
drgn-tools 2.0.1+1.el9, drgn 0.0.30 (using Python 3.9.21, elfutils 0.191, with libkdumpfile), with CTF
Loaded CTF debuginfo in in 0.790s
Running module ls... completed in 0.002s
Running module ls... completed in 0.005s
corelens total runtime: 0.807s

Compared to the below, when it's just one module:

$ corelens /proc/kcore -M ls / -c
warning: Running corelens against a live system.
         Data may be inconsistent, or corelens may crash.
/:
        23 positive, 339 negative dentries

The version "2.0.1" is fake (we haven't released it yet), but it illustrates the idea. The version & release are separated by the + sign due to limitations in what Python allows for version names.

Orabug: 37503503