[WIP] Removed assembly scanning by adding a bootstrapper

[RagingKore]

Removed assembly scanning and 99% of DI dependency by adding a simple bootstrapper, that still needs to be registered since Validation and Response extensions will require access to validators and negotiators.

CarterOptions still contain the global hooks setup, but was considering moving those to the bootstraper too.

This also opens the door to delegate composition as we now depend on a CarterRoute, not the module.

Performance optimizations are included.

• Added CarterBootstrapper to help register and keep dependencies.
• Added CarterRoute to better flow the required information to the route builder.
• Refactored CarterModule to build the before/after pipeline immediately.
• Fixed extensions to now resolve the bootstrapper.
• Removed DefaultValidatorLocator and added required logic to bootstrapper.
• Refactored CarterDiagnostics to a static function.

This targets #115 and somewhat supersedes #116 and #121.

[RagingKore]

Maybe it would be nice to keep backward compatibility by allowing a way to still run assembly scanning.

[RagingKore]

This targets #115 and somewhat supersedes #116 and #121.

[jchannon]

@thefringeninja fancy giving this some 👀

[jchannon]

What we really need to do is setup a windows box and run some profiling on this PR comparing it to master

[jchannon]

I wonder if we should tackle the old "scoped" issue with a bootstrapper somehow so we could get rid of the if (bootstrapper != null) and maybe if the collections are empty on the bootstrapper we do the assembly scanning anyway??

[RagingKore]

That was the idea, I just waited a bit to get feedback since it will still require a bit of work and I wanted to make sure that we can continue down this road.

[jchannon]

We have CarterConfigurator which I think will fix the ass scanning