Fix: pengine: Correctly search failcount (for real this time)

The point of this patch is to map resource failures to their
clone parent when calculating failcounts. Previously this was
done by using the clone prefix name, but this can lead to
weird instances where unrelated resources with the same
prefix in their name have their failcounts associated with
one another.  To avoid this, we verify the parent of the
matched resources are the same to verify the match is relevant
before updating failcount information.
Merge pull request #494 from davidvossel/master

Fix: pengine: Correctly search failcount (for real this time)