Add docker-workflow plugin to the managed set (#2464)

* Add docker-workflow plugin to managed set

* Remove docker-commons from sample-plugin dependencies

README advises that the dependencies in the sample plugin should be
maintained as we would any other plugin, with the top level
dependencies declared and the transitive dependencies calculated by
Maven.

Since docker-workflow depends on docker-commons, we don't need to
declare docker-commons in the sample plugin.

---------

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

bom-weekly/pom.xml

@@ -511,6 +511,11 @@
         <artifactId>docker-java-api</artifactId>
         <version>3.3.1-79.v20b_53427e041</version>
       </dependency>
+      <dependency>
+        <groupId>org.jenkins-ci.plugins</groupId>
+        <artifactId>docker-workflow</artifactId>
+        <version>572.v950f58993843</version>
+      </dependency>
       <dependency>
         <groupId>org.jenkins-ci.plugins</groupId>
         <artifactId>durable-task</artifactId>

sample-plugin/pom.xml

@@ -421,12 +421,12 @@
     </dependency>
     <dependency>
       <groupId>org.jenkins-ci.plugins</groupId>
-      <artifactId>docker-commons</artifactId>
+      <artifactId>docker-java-api</artifactId>
       <scope>test</scope>
     </dependency>
     <dependency>
       <groupId>org.jenkins-ci.plugins</groupId>
-      <artifactId>docker-java-api</artifactId>
+      <artifactId>docker-workflow</artifactId>
       <scope>test</scope>
     </dependency>
     <dependency>