Validate bindingType property (supported in Camunda 8.6+)

[jfriedenstab]

Problem you would like to solve

The new binding type deployment will only be supported by Zeebe 8.6 or newer. Users should be warned if they're using the new binding type in their BPMN process, but have selected a lower execution platform version.

Proposed solution

Add a new linting rule that warns the user if the binding type selected for a called process, called decision or linked form is not yet supported by the current execution platform version, for example:
A <Call Activity> with <Binding: Deployment> is only supported by Camunda 8.6 or newer

Alternatives considered

none

Additional context

• part of https://github.com/camunda/product-hub/issues/1920
• relates to Support bindingType for called processes/decisions/forms #4385

[wollefitz]

Update July 24

@jfriedenstab to clarify status of this issue / if it will make it before the 8.6-alpha4 release

[barmac]

I see that this is not implemented yet, so it's not coming as part of 8.6-alpha.4. I think it's quite unfortunate that the users can already use the new property, but are left in the dark about the support of the feature.

[barmac]

I'm moving this to ready.

[barmac]

Assigning @philippfromme as the assignee of #4385. Feel free to drop it if you don't have capacity.

[jfriedenstab]

Thanks, @barmac! Is there any chance that this could be implemented in the next days, @philippfromme? Then we could still try to include it in the release.

[philippfromme]

@jfriedenstab I'm on it!

[jfriedenstab]

Great, thank you! 🙂

[philippfromme]

Pull requests incoming:

• feat: lint zeebe:bindingType bpmnlint-plugin-camunda-compat#169
• feat: lint zeebe:bindingType linting#112

[barmac]

In that case, we may also include it in #4439

[philippfromme]

In that case, we may also include it in #4439

Yes, I'd like that.

[barmac]

I've updated the milestone since this is shipped with the current release.