Make Bootstrap and registration api its own module #863
Description
Right now both are defined into the core layer but have to initialize several components of the library, including the API layer, which is supposed to be on top.
API depends on Core, not the reverse.
Currently Boostrap.kt relies on the Entry.kt generated when building the project to initialize the API wrapper.
This shouldn't be the responsibility of the Entry to do so, as it should only be initializing user code.
I propose to move everything related to Bootstrap and the registration API to a different module that would on top of both the core and api module.
This way we will be able directly initialize the API from it instead of the indirection through Entry.
It would also allow to simplify some area, like the VariantMapper moving to the internal module and directly appended by the Bootstrap, maybe even merged with the TypeManager.