Align module generation and skip configuration by default

[LukasPaczos]

Closes #14. Closes #18.

This PR consolidates module generation from both Maps and Nav SDKs and ships the provider in the common library.

This removes the separation of the module types - now all of them are under one enum constant. This not only helps to make the provider generic but also will allow us to write simpler docs.

One downside is, that all params providers will need to overwrite all module types, even if particular SDK is not supporting them. For example, Navigation SDKs param provider will look something like:

private fun paramsProvider(type: MapboxModuleType): Array<Pair<Class<*>?, Any?>> {
    return when (type) {
        MapboxModuleType.NavigationRouter -> ...
        MapboxModuleType.NavigationOffboardRouter -> ...
        MapboxModuleType.NavigationOnboardRouter -> ...
        MapboxModuleType.NavigationTripNotification -> ...
        else -> throw RuntimeException("not supported: ${type.name}")
    }
}

however, we'll never hit the else branch, unless we make the mistake ourselves and it should be caught quickly.

[LukasPaczos]

This takes #21 into consideration already @Lebedinsky. Depending on which is merged first, we can resolve the conflicts.

[tobrun]

One downside is, that all params providers will need to overwrite all module types

I'm fine with this as a drawback, maybe some kind of adapter approach would work here.

[LukasPaczos]

Ready for another round.

[LukasPaczos]

I added a bunch more of sanity tests, example usage in the docs and cleaned up the code.

[tobrun]

every time you feel the need to write a comment, you can consider writing a function instead