Stunner - BPMN Serialization reusing ID

Designer generate and regenerate after every save IDs for some elements and not using this ID anywhere. if ID is not used anywhere in the process it should be removed. For example Element Documentation has attribute id, but this id is not used anywhere else to refer to this documentation and so it can be removed.

Attached Example files before/after the fix

BeforeChangesInit.bpmn - process saved in Kogito webapp without changes
BeforeChangesResult.bpmn - process saved in Kogito webapp after small change

WithFixInit.bpmn - process saved in Kogito webapp with fix for the first time (IDs removed)
WithFixResult.bpmn - process saved in Kogito webapp with fix after small change

BeforeFix.diff - Diff file generated from BeforeChangesInit.bpmn and BeforeChangesResult.bpmn
AfterFix.diff - Diff file generated from WithFixInit.bpmn and WithFixResult.bpmn

Acceptance Criteria

• IDs with no usage shouldn't be generated.
• Open any BPMN process generated in VS Code plugin, made small change and save
• In resulted XML shouldn't be changed IDs which never used for elements:
  • Documentaion
  • LaneSet
  • ioSpecification
  • inputSet
  • outputSet
  • dataInputAssociation
  • DataOutputAssociation
  • Assignment
  • TimerEventDefinition
  • CompensateEventDefinition
  • SignalEventDefinition
  • errorEventDefinition
  • completionCondition
  • messageEventDefinition
  • escalationEventDefinition
  • conditionalEventDefinition
  • terminateEventDefinition
  • MultiInstanceLoopCharacteristics
  • Potential Owner (User Task → Actor property)
  • FormalExpression tags such as:
    • CompletionCondition
    • ConditionExpression
    • Condition
    • TimeDate
    • TimeDuration
    • from
    • to

Expected Result

After save no one element will change ID if ID is not used in other places.