fix: ignore non-FEEL properties in the FEEL rule

[jarekdanielak]

Closes #53

Proposed Changes

Ignore non-FEEL properties even if they are formatted like a FEEL expression.

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

This PR updates the Camunda Cloud feel bpmnlint rule to avoid false positives by skipping FEEL linting for properties that are not intended to contain FEEL expressions, even if their string values start with =.

Changes:

• Extend the FEEL rule with global and type-specific ignored property lists (e.g. name, zeebe:Input#target, zeebe:Header#key/value).
• Adjust FEEL-property detection to consider the owning element type (node.$type) when deciding whether to lint.
• Add test cases ensuring FEEL-like strings in non-FEEL properties are treated as valid (ignored) inputs.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
test/camunda-cloud/feel.spec.js	Adds regression tests for FEEL-like values on properties that should be ignored by the FEEL rule.
rules/camunda-cloud/feel.js	Introduces ignored-property filtering (global + per $type) before running FEEL linting.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.