fix: allow maven to publish without implicit task ordering

[iBotPeaches]

This fixes 2 things.

A problem was found with the configuration of task ':brut.apktool:apktool-cli:shadowJar' (type 'Jar').
  - Gradle detected a problem with the following location: 'Apktool/brut.apktool/apktool-cli/build/libs/apktool-cli.jar'.
    
    Reason: Task ':brut.apktool:apktool-cli:generateMetadataFileForMavenJavaPublication' uses this output of task ':brut.apktool:apktool-cli:shadowJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

Execution failed for task ':brut.apktool:apktool-cli:generateMetadataFileForMavenJavaPublication'.
> java.io.FileNotFoundException: Apktool/brut.apktool/apktool-cli/build/libs/apktool-cli-javadoc.jar (No such file or directory)

---

• Adapted with some ugly verbose config to depend Maven tasks on the completion of shadowJar
• Ensured the clean build directory doesn't purge sources/javadoc (which is only apparent on maven publish)