Should dependency scanning in DependencyContextAssemblyCatalog consider transitive deps? #360
Description
While working on ethankershaw/fix-11 I was puzzled why I was needing to manually add the modules via configurator instead of them being picked up by scanning. I debugged it and determined that the Carter.SirenNegotiator.Samples project was getting it's Carter reference transitively through the Carter.SirenNegotiator project reference. Carter.DependencyContextAssemblyCatalog.IsReferencingCarter is only checking immediate dependencies. As soon as I added a direct project reference from Carter.SirenNegotiator.Samples to the Carter project in the submodule referenced there, all was well with module registration by scanning.