This Camel route must now iterates on all microservice objects to send mutliple queries to dcae to undeploy the microservices in the right order (the one defined in the loop)

The dcaeDeploymentStatusUrl and dcaeDeploymentId must be updated accordingly in the new microservices object fields.

Note: The approach could be to create a new Camel code on top of the existing undeploy-loop flow as this one is already designed for a simple blueprint (may be a copy of that code would have to be done). The code must be backward compatible, meaning that a blueprint containing multiple microservices should still work