Add DryIocZero compile-time capabilities to DryIoc source package

[dadhi]

Here is the thread:
https://twitter.com/jeremydmiller/status/1106694539056680965?s=19

[dadhi]

To consider:

• There only one of the packages can be installed: DryIoc.dll or DryIoc source, probably it is fine
• It will allow non-breaking drop-in switch from run-time DryIoc.dll to DryIoc with compile-time capabilities.
• If you don't want, you may not use compile-time DI - just use source code DryIoc as before.
• You will be able to use any normal typed runtime registration for the compile-time registered placeholder - currently DryIoc zero supports instance and delegate registrations only.
• All extensions already have a source code packages compatible with DryIoc source package. No need for separate set of extensions for DIZero. That's mean DI.MS.DI.src (ResolveMany with Meta does NOT work but collection with Meta does work #100) will work too.

Development:

• No need to dublicate the subset of container (this is the most annoying and error prone part), just reference the same Container.cs maybe with addional #ifoptions.
• Less code to maintain
• There is an addional compile-time only dependency to ExpressionToCodeLib
• Harder to benchmark dll vs. source package cause they could not be used in the same app. But we can select third-party lib as baseline to compare :)

[dadhi]

Should help with https://ryandavis.io/adventures-in-low-overhead-dependency-injection-using-dryioczero/

[dadhi]

PR #210

[dadhi]

I have added the DIZero capabilities to DI source package but the main PITA is still T4 - likely we need other template system. Let's take this separately.