Add support for setting a version tag for a BPMN process

[jfriedenstab]

Problem you would like to solve

As a Camunda 8 user, I'd like to be able to specify a custom version tag for a BPMN process (so that the process will be available under this version tag when it gets deployed later on and can be referenced from a call activity using versionTag binding).

Proposed solution

• A new (optional) input field "Version tag" is added to the "General" section of the properties panel for a process/participant in a BPMN diagram.
• The version tag is stored in the value attribute of a zeebe:versionTag extension element:

  <bpmn:process id="test-process" name="test process" isExecutable="true">
      <bpmn:extensionElements>
          <zeebe:versionTag value="v1.0.0" />
      </bpmn:extensionElements>
  </bpmn:process>

Additional context

• part of [EPIC] Support version tag binding for linked resources camunda#19812
• relates to Add support for setting a version tag for a DMN decision #4454
• relates to Add support for versionTag binding for call activities #4460