Explicitly declare bundled artifacts (#1321)

* Explicitly declare bundled artifacts

Do not allow additions to the bundled dependencies without a change to
the list of bundledArtifacts.  Avoid the mistakes made in the past when
a new transitive dependency was inadvertently added to the plugin and
bundled into the hpi / jpi file.

Draft until the release of pull request:

* jenkinsci/maven-hpi-plugin#771

Testing done:

Confirmed that compilation passes and a single test passes.  Rely on
ci.jenkins.io for more complete testing

* Use parent pom 5.22 with strictBundledArtifacts

---------

Co-authored-by: git-client-user <git-client-user@example.com>

Author: MarkEWaite

pom.xml

@@ -5,7 +5,7 @@
   <parent>
     <groupId>org.jenkins-ci.plugins</groupId>
     <artifactId>plugin</artifactId>
-    <version>5.19</version>
+    <version>5.22</version>
     <relativePath />
   </parent>
 
@@ -37,6 +37,8 @@
     <!-- Character set tests fail unless file.encoding is set -->
     <argLine>-Dfile.encoding=${project.build.sourceEncoding}</argLine>
     <gitHubRepo>jenkinsci/${project.artifactId}-plugin</gitHubRepo>
+    <hpi.bundledArtifacts>JavaEWAH,org.eclipse.jgit,org.eclipse.jgit.http.apache,org.eclipse.jgit.http.server,org.eclipse.jgit.lfs,org.eclipse.jgit.ssh.apache</hpi.bundledArtifacts>
+    <hpi.strictBundledArtifacts>true</hpi.strictBundledArtifacts>
     <!-- https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/ -->
     <jenkins.baseline>2.504</jenkins.baseline>
     <jenkins.version>${jenkins.baseline}.1</jenkins.version>