Show how to avoid the double patch bump

The `release` task also bumps, a patch one by default.
So just don't use `markNextVersion` within the release process.
It's for manually marking a version for the future.

Show how to avoid atlassian-labs/db-replica#77

src/test/kotlin/com/atlassian/performance/tools/license/ReleaseTest.kt

@@ -25,15 +25,7 @@ class ReleaseTest {
         project.git.addOrigin(safelyPushableRemote)
         project.git.push().call()
 
-        val markNextVersion = project.buildTask(
-            "markNextVersion",
-            "-Prelease.incrementer=incrementPatch",
-            "-Prelease.localOnly",
-            "--stacktrace"
-        )
-        assertThat(markNextVersion?.task(":markNextVersion")?.outcome).isEqualTo(SUCCESS)
-
-        val release = project.buildTask("release", "--stacktrace")
+        val release = project.buildTask("release", "-Prelease.incrementer=incrementPatch", "--stacktrace")
         assertThat(release?.task(":release")?.outcome).isEqualTo(SUCCESS)
 
         val currentVersion = project.buildTask("currentVersion")