Add Gradle-like API for adding dependencies

[ileasile]

Fix #367

[ileasile]

If we try to add library immediately, recursive execution happens - execution DURING another execution. We don't know how to handle it, because we use previous script instances for evaluation, and it's not clear what to do without them. So we just schedule the execution to the end of the current execution.

[altavir]

It is not clear if this uses gradle resolver or maven resolver. It works differently for mpp libraries. I think the notation is great in any case, but if it uses maven resolver, there must be a warning about jvm suffix.

[nikolay-egorov]

Looks neat!

[ileasile]

I'm concerned about names too: it's not clear what gradle means, it sounds like we configure Gradle, not kernel. But I can't come up with a better name for this DSL entry point
Maven resolver is used underhood, yes.

[altavir]

I'm concerned about names too: it's not clear what gradle means, it sounds like we configure Gradle, not kernel. But I can't come up with a better name for this DSL entry point Maven resolver is used underhood, yes.

maybe something like requires? It does not matter how it is called since you copy only what is inside.

[ileasile]

1. gradle - clear what you should write inside but doesn't explain the purpose
2. gradleLike[Conf] - better, but verbose
3. requires - good borrowing from JS modules, but there is require in Kotlin, and may be misleading
4. config, configure, provide - not bad, but too generic
5. build - looks like a compromise variant
6. dependencyResolutionManagement - name of block in settings.gradle[.kts] that is actually responsible for dependency management

Let's choose something please

[altavir]

@ileasile I think it is better to discuss in slack. Maybe a vote.

I do not think that the outer scope should match how it looks in Gradle because people do not copy the whole block, they copy its contents. Also dependencyResolutionManagement is not used in project config, only in settings.

What about dependsOn{ }?

[ileasile]

Final version of API:

USE {
	repositories {
		mavenCentral()
	}
	dependencies {
		implementation("io.github.config4k:config4k:0.4.2")
	}
}

Or in integration:

internal class Integration : JupyterIntegration() {
    
    override fun Builder.onLoaded() {
        repositories {
		mavenCentral()
	}
	dependencies {
		implementation("io.github.config4k:config4k:0.4.2")
	}
    }
}