MLE-12345 Fixing weird plugin classpath issue

This allows for test-app to be a subproject, allowing a developer to run `mlDeploy` from the root directory.

Author: rjrudin

build.gradle

@@ -1,7 +1,19 @@
+buildscript {
+  repositories {
+    mavenCentral()
+  }
+  dependencies {
+    // Add jaxen to buildscript classpath to prevent NoClassDefFoundError when shadow plugin interferes with
+    // ml-data-hub plugin execution. It is not yet known why the shadow plugin causes this problem or why it's
+    // specific to the jaxen library, but this resolves the problem.
+    classpath 'jaxen:jaxen:2.0.0'
+  }
+}
+
 plugins {
   id 'java'
   id 'net.saliman.properties' version '1.5.2'
-  id 'com.gradleup.shadow' version '8.3.4'
+  id 'com.gradleup.shadow' version '9.2.2'
 
   // Only used for testing
   id 'jacoco'

settings.gradle

@@ -1,2 +1,2 @@
 rootProject.name = 'kafka-connect-marklogic'
-
+include "test-app"

test-app/.gitignore

@@ -1,2 +1,5 @@
 src/main/hub-internal-config
 src/main/entity-config
+gradle
+gradlew
+gradlew.bat