Fix crate-node cli script for non-release builds
Fix crate-node cli script for non-release builds

On non-release builds the `bin/crate-node` script resulted in an error
because it couldn't find the `NodeToolCli`. This couldn't be found
because the `crate-app.jar` that was referenced in the `classpath`
didn't exist. It was called something like
`crate-app-4.1.0-SNAPSHOT-b144b29bea.jar` instead.

This sets the `archiveFileName` to `crate-app.jar` so that non-release
builds have the same jar name as release builds do.

Adapting the classpath of the `crate-node` script dynamically didn't
work out. Changing it to something like:

    classpath = sourceSets.main.runtimeClasspath + files("lib/${jar.archiveFileName.get()")

Would require a dependency on the jar task which results in a cyclic
dependency and breaks the build.

EvilMcJerkface/crate,EvilMcJerkface/crate,EvilMcJerkface/crate,crate/crate,crate/crate,crate/crate