fix(plugins): declare missing :crypto and :common jar deps for binaryRelease

Per review on PR #6738 (halibobo1205): the binaryRelease Jar task zips up
runtimeClasspath contents, which on this branch includes :crypto:jar and
:common:jar (introduced by #6637), but the task only declared dependsOn on
:protocol:jar and :platform:jar. Gradle was emitting an implicit_dependency
warning and disabling execution optimizations to compensate.

Reproduced locally:
  $ ./gradlew clean && ./gradlew :plugins:buildToolkitJar
  > Cannot expand ZIP '.../crypto/build/libs/crypto-1.0.0.jar' as it does
    not exist.

Add :crypto:jar and :common:jar to dependsOn so partial / parallel /
incremental builds can no longer race against missing dependency jars.

Verified:
- ./gradlew clean :plugins:buildToolkitJar passes with --warning-mode all
  and no implicit_dependency warning
- Smoke (db archive -d <empty>) still exits 0 on x86 docker
- :plugins:test, checkstyleMain, checkstyleTest all pass

Author: Barbatos

plugins/build.gradle

@@ -141,7 +141,13 @@ def binaryRelease(taskName, jarName, mainClass) {
         from(sourceSets.main.output) {
             include "/**"
         }
-        dependsOn (project(':protocol').jar, project(':platform').jar) // explicit_dependency
+        // Fat jar zips up runtimeClasspath, which includes the jar outputs of
+        // every project dependency. Declare them all explicitly so Gradle does
+        // not warn about implicit_dependency and disable execution optimizations
+        // (and so partial / parallel builds cannot run binaryRelease before the
+        // dependency jars exist).
+        dependsOn (project(':protocol').jar, project(':platform').jar,
+                project(':crypto').jar, project(':common').jar) // explicit_dependency
         from {
             configurations.runtimeClasspath.collect { // https://docs.gradle.org/current/userguide/upgrading_version_6.html#changes_6.3
                 it.isDirectory() ? it : zipTree(it)