feat: support zeebe:calledDecision

[yT0n1]

related to camunda/camunda-modeler#5025

Proposed Changes

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[Copilot]

Pull Request Overview

Adds support for the new zeebe:calledDecision binding in the validator and covers it with tests.

• Extend valid binding types list to include zeebe:calledDecision
• Add two new tests: one for successful validation of called decision templates and one for error scenarios

Files not reviewed (2)

• test/fixtures/called-decision-broken.json: Language not supported
• test/fixtures/called-decision.json: Language not supported

Comments suppressed due to low confidence (1)

test/spec/validationSpec.js:509

• The negative test checks only overall validity but does not assert specific error messages or codes. To ensure the validator fails for the intended reasons, add assertions on the content of results (e.g., error messages or keys).

expect(valid).to.be.false;

[Copilot]

[nitpick] The test duplicates the full list of supported binding types, which makes it brittle if that list changes. Consider fetching the supported bindings from the validator or using a regex/assertion that only checks for the presence of 'zeebe:calledDecision' instead of hard-coding the entire list.

Suggested change

	message: 'invalid property.binding type "zeebe:taskDefinition:foo"; must be any of { property, zeebe:taskDefinition:type, zeebe:input, zeebe:output, zeebe:property, zeebe:taskHeader, bpmn:Message#property, bpmn:Message#zeebe:subscription#property, zeebe:taskDefinition, zeebe:calledElement, zeebe:linkedResource, zeebe:userTask, zeebe:calledDecision }'
	message: /invalid property\.binding type "zeebe:taskDefinition:foo"; must be any of .*zeebe:calledDecision.*/