Extract Jupyter dependencies to different module

[Jolanrensen]

It can be the case we now publish API calls that depend on Jupyter stuff such that a user has to implement the kotlin-jupyter-api themselves. That shouldn't be needed.

Similar to Kotlin Spark, we should put all Jupyter dependencies inside a separate module, like "dataframe-jupyter", which can then be used when users have %use dataframe in their notebooks.

[koperagen]

It's quite painful, there are some internal things that cannot become a part of the public API, so we'd have to create 3rd module for these common internals..? For now i fixed usages of jupyter classes outside "Integration.kt", that should be enough to not break things for users outside Jupyter Notebooks.

[Jolanrensen]

Similar to #100.

Could be done with "friend/associates modules"

[Jolanrensen]

Fixes #700

[Jolanrensen]

Duplicated by #775