Add docker-commons to the managed set (jenkinsci#2220)

* Add authentication-tokens plugin to managed set

Pin version 1.4 for 2.375.x

* Add docker-commons to managed set

* Test sample plugin with docker-commons

* Test with incremental 431.vef5777319e6b_

* Use docker commons 434.v3dc53576ec32

Thanks @jglick!

* Test docker-commons incremetal with test fix

jenkinsci/docker-commons-plugin#140 adapts the
docker-commons test to the UI improvement in Jenkins 2.413 and makes
it more resilient in case there are future changes in that area.

* Use docker commons 434.v3dc53576ec32 release

* Revert "Use docker commons 434.v3dc53576ec32 release"

The release does not include the test fix that is proposed in
jenkinsci/docker-commons-plugin#140

This reverts commit 077a294.

* Use docker-commons 439.va_3cb_0a_6a_fb_29

jenkinsci/docker-commons-plugin#140 fixes the
test issue on Jenkins 2.413 and later.

---------

Co-authored-by: Basil Crow <me@basilcrow.com>

bom-weekly/pom.xml

@@ -359,6 +359,11 @@
         <artifactId>display-url-api</artifactId>
         <version>2.3.7</version>
       </dependency>
+      <dependency>
+        <groupId>org.jenkins-ci.plugins</groupId>
+        <artifactId>docker-commons</artifactId>
+        <version>439.va_3cb_0a_6a_fb_29</version>
+      </dependency>
       <dependency>
         <groupId>org.jenkins-ci.plugins</groupId>
         <artifactId>docker-java-api</artifactId>

sample-plugin/pom.xml

@@ -280,6 +280,11 @@
       <artifactId>dashboard-view</artifactId>
       <scope>test</scope>
     </dependency>
+    <dependency>
+      <groupId>org.jenkins-ci.plugins</groupId>
+      <artifactId>docker-commons</artifactId>
+      <scope>test</scope>
+    </dependency>
     <dependency>
       <groupId>org.jenkins-ci.plugins</groupId>
       <artifactId>docker-java-api</artifactId>