Feature Request: Support javax.inject.Provider interop with LazyKt.lazy and dagger.Lazy

[andreasnomikos]

Motif promotes a coding model comprised of a big tree of small nested scopes so using some form of Lazy is usually not required.

javax.inject.Provider can be a direct standin replacement of Lazy as long as the original provider for Foo is not annotated with @DoNotCache

There might however still be cases where for interop reasons with Dagger libraries or kotlin libraries we might want to provide kotlin.Lazy or dagger.Lazy bindings or at a minimum some extensions to convert motif Providers to the above interfaces.

From an optimizations perspective the only dagger opt I am aware of that is relevant is that if you try to prime a dagger.Lazy with a javax.inject.Provider that is already a dagger.Lazy then the implementation will avoid stacking the 2 lazies and will only use the original