Allow transitive dependencies

[tkellogg]

Moq allows passing constructor args to mock instances via
new Mock<Foo>(arg1, arg2, ...). This pull request enables doing this
for automocker, enhancing the "auto" part of "automocker".

Why do this? Because forcing every class to have an interface seems
unreasonable. Feel free to subscribe to whatever philosophy you prefer,
but the interface-to-class pairing does generate a lot of boilerplate.
Just as Moq allows as many scenarios as possible, Moq.Contrib should
also.

[Keboo]

Created #87 as a proposed cleanup instead of disabling this here.

[Keboo]

There is a bit of a disjoint here. If this should be public then we should remove the CA1812 above and update the comment, or this could go back to internal

[tkellogg]

Hold up on merging this. It doesn't handle recursive dependencies... working on it.

[adamhewitt627]

LGTM so far - what is the version number impact? Thinking particularly of the .Use<T>(null).

[tkellogg]

Alright, I handled recursive object graphs by throwing an error. We could probably get more robust in that area, but this is a big start.

@adamhewitt627 I believe this doesn't break any behavior. This uses (basically) the public .Get(childType) for dependencies, so it'll use the normal resolution rules to obtain an instance. That means if you did any form of .Use(), it'll use that registered value. It's basically a full DI/IoC container now, except it mocks instead of throwing an exception when it runs into an unknown type.