Make tRip be optional, but the main DI/IoC dependency

[miere]

Today implementation design makes Kikaha directly dependent on tRip for Dependency Injection. The idea is open the gates to another DI implementations, such as Spring and Guice.

To make this viable, kikaha-core will provide a set of interfaces called Dependency Injection Wrapper API. UndertowServer.java class, that starts up embedded Undertow server will become dependent on these interfaces. Developers will be able to implement these interfaces and make Kikaha compatible with another DI containers.

The core components the Dependency Injection Wrapper API:

• Allow kikaha-core to retrieve all kikaha.core.api implementations at deployment time
• Allow kikaha-urouting to retrieve all kikaha.urouting.api implementations at deployment time
• Allow kikaha-urouting to retrieve needed data to generate the wrapper classes the will be deployed into the kikaha-core module.

[miere]

Its been about 9 months since last update on this issue and, as the user's feedback comes, this issue took another direction. In order to keep Kikaha simple, it will merge the main tRip's IoC routine into the Kikaha's core. tRip already has extension support and it will be kept on Kikaha to allow module developers to create Guice and Spring extensions. The only out-of-box extension that Kikaha will offer is the JSR-330 CDI implementation.