BPMN Editor removes output variables from task without alerting or throwing error

Main Issue:
If you open a task, add two output variables with the same "name" but different "Target" variables, you can still save the process. But when you open the process again, and check the same task the duplicated output variable is not on the task anymore.

Migration feature possibly impacted by the issue above:

• Migration is affected by this. If you migrate the legacy process with a task that contains two output variables with the same name, one of the variables is removed from the migrated version without any notification.
  Note the missing "approved_" on the migrated version of the process attached.

Observation: This only happens with the output variable. The new editor does not allow creating two input variables with the same name, it throws an alert: "A Data Input with this name already exists". It is possible to create two output variables with the same name on the legacy designer.

How to test at runtime

1. Create Start -> User Task -> End process
2. Create process variables `p_var1:String` and `p_var2:String`
3. For User Task set up Data Assignments in the following way:
4. Build and deploy the project, execute process, clam user task and provide any value for var1
5. When process is finished look at it's Process Info, both `p_var1:String` and `p_var2:String` should have the same value