Collapse dependency failures into Class level failures

When a Class has a failed dependency, every individual resource in the class generates a notice level message about the dependency failure and a warning level message about skipping the resource, as well as a skip event in the report. This can generate a large number of messages and a large report if there are many dependencies, or multiple layers of dependencies.

At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports.

If possible, all of the skipped resources should be collapsed into the containing class and the messages and skip event should be done at the class level. It looks like the most recent work on this was done in PUP-3930 and commit 32e2bf2.