fix: workaround decorator ordering

extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/ChangeDeploymentTriggerDecorator.java

@@ -1,5 +1,9 @@
 package io.quarkus.kubernetes.deployment;
 
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+
 import io.dekorate.kubernetes.decorator.Decorator;
 import io.dekorate.openshift.decorator.ApplyDeploymentTriggerDecorator;
 
@@ -11,6 +15,13 @@ public ChangeDeploymentTriggerDecorator(String containerName, String imageStream
 
     @Override
     public Class<? extends Decorator>[] after() {
-        return new Class[] { ApplyDeploymentTriggerDecorator.class, RemoveDeploymentTriggerDecorator.class };
+        //There is a series of issues in dekorate that breaks ordering of the ApplyDeploymentTriggerDecorator.
+        //The problem is that the ApplyDeploymentTrigger decorator depends any a lot of irrelevant Decorators
+        //So, this one needs to inherit the same decorator or else we can't guarantee that its executed after
+        //the ApplyDeploymentTriggerDecorator.
+        List<Class<? extends Decorator>> classes = new ArrayList<>(Arrays.asList(super.after()));
+        classes.add(ApplyDeploymentTriggerDecorator.class);
+        classes.add(RemoveBuilderImageResourceDecorator.class);
+        return classes.toArray(new Class[classes.size()]);
     }
 }