Stunner - Service Tasks deployments

This task follows up on:

• Follows up on JBPM-5649
• Addresses part of JBPM-7037

It means, as from JBPM-5649 the Service Tasks are supported in Stunner, but it's not yet deploying the Work Item Definitions (WID) as the current jbpm-designer does, which is a blocker as it does not allow to just rely on the Stunner editor for the BPMN authoring. So this ticket will focus on the deployment stuff that Stunner is missing, considering out of scope the other tasks identified in JBPM-7037.

This way the goals for this task are:

• Once creating or opening a BPMN process in Stunner, it will perform a remote call to the
  backend in order to figure out if work item definitions have been already deployed and installed for the active project. If no service tasks found, it will start the deployment and installation process. Otherwise, no deployment neither installation actions will be done.

• The predicate used to figure if service tasks have been already deployed and installed for the active project relies on checking on the filesystem and looking for any work item definition asset (.wid) is found, it means this predicate does not consider the WID's name/s that the asset contain (eg: Email, Log)

• The deployment operation will consume from:
  • Default built-in WID provided by the designer
  • Remote service task repository specified on the JVM system properties, if any

• The deployment operation consists of:
  • Deploying the WID assets into the active project's FS (.wid, images, libraries)
  • Installation of the Maven project and libraries into active's KIE project