Mention pmd-java deps explicitly

They're transitively gotten from
pmd-core, but for some use cases
this is nicer

eg `mvn install -pl pmd-java`, given
that pmd-core was already installed
locally, should succeed. If the dependencies
are not mentioned explicitly, for some
reason this fails.

Before #2614, pmd-core was shaded with
its dependencies and this wasn't necessary

pmd-core/pom.xml

@@ -109,7 +109,6 @@
         <dependency>
             <groupId>org.checkerframework</groupId>
             <artifactId>checker-qual</artifactId>
-            <version>2.5.2</version>
         </dependency>
         <dependency>
             <groupId>org.pcollections</groupId>

pmd-java/pom.xml

@@ -128,6 +128,19 @@
             <groupId>org.apache.commons</groupId>
             <artifactId>commons-lang3</artifactId>
         </dependency>
+        <dependency>
+            <groupId>org.checkerframework</groupId>
+            <artifactId>checker-qual</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>net.sf.saxon</groupId>
+            <artifactId>Saxon-HE</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.pcollections</groupId>
+            <artifactId>pcollections</artifactId>
+        </dependency>
+
 
         <!-- TEST DEPENDENCIES -->
         <dependency>

pom.xml

@@ -670,6 +670,11 @@
                 <artifactId>pmd-core</artifactId>
                 <version>${project.version}</version>
             </dependency>
+            <dependency>
+                <groupId>org.checkerframework</groupId>
+                <artifactId>checker-qual</artifactId>
+                <version>2.5.2</version>
+            </dependency>
             <dependency>
                 <groupId>net.sf.saxon</groupId>
                 <artifactId>Saxon-HE</artifactId>