workflow_RHELvmcore: run analyze_VMcore too

analyze_VMcore does the following:

* extracts oops from vmcore-dmesg.txt
  (or from vmcore, if vmcore-dmesg.txt is missing);
  creates "kernel" element.
* generates dedup hashes.
* generates pkg_* elements.

These steps probably aren't necessary if we take the usual step
of running report_RHTSupport: RHTSupport people don't absolutely
need that data. (However, I did not test whether report_RHTSupport
actually works w/o analyze_VMcore).

But for Machine Check Exceptions, oops extraction is crucial:
without seeing "backtrace" element, which in this case shows
MCE message, user won't realize he has a hardware issue,
and will still contact RHTSupport, only to be told by them,
after analysis, "look at your CPU/RAM, they seem to be faulty"
- exactly the scenario we want to avoid (we want user
to not waste his and RHTSupport's time - the problem is known).

Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
Merge pull request #215 from abrt/gh214

workflow_RHELvmcore: run analyze_VMcore too