Improve ServiceVerificationHandler missing dependency reporting

The reporting of missing services by the ServiceVerificationHandler is overly verbose and sometimes hides more important information in a mountain of detail. To improve:

1) Reporting of services that could not start due to a transitive missing dependency should be reported in a separate property in the failure description ModelNode object than the failure of services that have immediate unavailable dependencies.

2) If any services are missing transitive dependencies, the SVH should scan the ServiceContainer looking for any services that could not start due to an immediate dependency being missing. Use those to create a global list of missing services to include with the "transitive missing" failure description. That's better data than the current "JBAS014861: <one or more transitive dependencies>".

3) Improve the formatting of the list of services that are missing transitive dependencies, to make it less mindlessly repetitive.

4) Probably most importantly, tracking any services names already reported as being missing or failed in the overall SVH failure description. When the global list of missing services is prepared in 2) above, compare it to this list. If the two sets are identical, don't bother reporting the "missing transitive dependency" problems. That information is unlikely to be useful, since the problem services are already reported in the "missing immediate dependency" section of the failure description.