After having to deal with Python scripts (See #10), it became clear that some (if not all) scripts should be re-engineered.

I'm opening this issue to discuss about what approach we can go to fix it. I mapped out a few available paths:

1. Rewrite the current Python scripts

This would be the easier, as it's just re-engineering the current Python scripts. But it'd require help from other contributors to do.

2. Write a new toolchain in a JVM scripting language.

This would make the job easier for the Java developers... if we can all agree between Groovy, KotlinScript, JavaScript (Rhino, Nashorn, GraalVM), Scala, Lua (LuaJ, Cobalt), Python (Jython), etc... as the scripting language for the toolchain. It'd require a bit more time to port Python to it.

3. Write a new toolchain as a Gradle plugin.

Hey, people at MinecraftForge, Sponge and FabricMC did it already. We can implement the toolchain as a separate Gradle plugin. It'd be the most effort, since we'd need a separate repository to maintain the Gradle plugin and fixes would most likely take hours instead of minutes, but it'd give out the best user experience.

4. Port it to another different language at all.

The last alternative would be porting it to a different language that most core RethinkDB developers could help, such as JavaScript (for example, running on Node.js). This option could take as much time as option 2 or 3, but fixes would most likely be made by pretty much any RethinkDB maintainer.