JavaScript: Remove build cache from npmBuild/npmFixturesBuild

Caching npmBuild caused version.txt to retain stale timestamps from
previous builds, which could result in the release JAR referencing a
non-existent npm version at runtime. The onlyIf guard on npmPublish
also prevented snapshot publishing in CI's two-invocation flow since
npmBuild was always UP-TO-DATE in the second invocation.

Keep build cache enabled only for npmTest, which is the expensive task
and has no versioning side effects.

Author: knutwannheden

rewrite-javascript/build.gradle.kts

@@ -124,7 +124,6 @@ val npmBuild = tasks.register<NpmTask>("npmBuild") {
     inputs.files(fileTree("rewrite/src"))
         .withPathSensitivity(PathSensitivity.RELATIVE)
     outputs.dir(file("rewrite/dist/"))
-    outputs.cacheIf { true }
 
     val versionTxt = file("src/main/resources/META-INF/version.txt")
     outputs.file(versionTxt)
@@ -174,7 +173,6 @@ val npmFixturesBuild = tasks.register<NpmTask>("npmFixturesBuild") {
     inputs.files(fileTree("rewrite/fixtures"))
         .withPathSensitivity(PathSensitivity.RELATIVE)
     outputs.dir(file("rewrite/dist-fixtures/"))
-    outputs.cacheIf { true }
 
     args = listOf("run", "build:fixtures")
 }
@@ -227,11 +225,6 @@ val npmPublish = tasks.register<NpmTask>("npmPublish") {
     args = provider { listOf("publish", npmPack.get().archiveFile.get().asFile.absolutePath) }
     if (!project.hasProperty("releasing")) {
         args.addAll("--tag", "next")
-        // Skip publishing when nothing changed in the JavaScript implementation.
-        // When npmBuild is restored from the build cache, version.txt retains the
-        // timestamp from the original build, causing a conflict with the previously
-        // published version on npmjs.
-        onlyIf { npmBuild.get().state.didWork }
     }
 
     workingDir.set(file("rewrite"))