Make sure itests are triggered after studio_master and studio_maintenance maven deployments

maven deployments of test jars is triggered after trigger of itests, which have a quiet period of 1 min, but may be not enough to benefit from deployed jars: see for instance https://qapriv.nuxeo.org/jenkins/job/nuxeo-studio-maintenance-itests-5.5/51/ triggered before https://qapriv.nuxeo.org/jenkins/job/nuxeo-studio-maintenance/320/ is done deploying.

Since the "Process Job DSLs" action does not seem to be available in orderable build actions, this cannot be moved after maven jenkins re-deployments => maybe create another job for these.

Note the job will still have to checkout studio code, because the DSL relies on class com.nuxeo.studio.client.model.TARGET_PLATFORM.

+ maybe check generated jobs names (currently based on the caller job name)