Replace ServiceRegistry by @Inject based DI on ScriptPluginFactoryProvider SPI

[bamboo]

There are two main reasons for it:

• ServiceRegistry is an internal interface and as such it should not be part of an API
• to make all dependencies explicit at the KotlinScriptPluginFactoryProvider level

In order to evolve the SPI interface without binary breakage:

1. introduce new method on core SPI but don't call it just yet
2. implement the new method on gsk and ship new minor release
3. update core to new gsk release and call the new method
   • remove old method and ship new nightly (breaks source gsk compatibility!)
   • update gradle/gradle-script-kotlin branch to latest gradle
4. remove old implementation from gsk when new core nightly comes out