feat: allow to pass FEEL language context via context

[Buckwich]

Related to camunda/camunda-modeler#4809

Proposed Changes

accept feelLanguageContext as an input for parserDialect and other feel specific fields

Test via:

npx @bpmn-io/sr bpmn-io/bpmn-js-properties-panel#4809-set-parser-dialect-camunda-context -l bpmn-io/properties-panel#4809-configurable-parser-dialect-context (doesn't work)

Manually link to bpmn-io/bpmn-js-properties-panel#4809-set-parser-dialect-camunda-context.

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}

[Buckwich]

• camunda dialect is no longer applied to the feel popup after fixing merge conflicts, need to look into it again

[nikku]

Thanks for addressing the merge conflicts. I'll look into this tomorrow. ✔️

[barmac]

I've added an @bpmn-io/sr script in the top comment for easy testing of the change.

[barmac]

Hmm the script fails due to missing context export, but it seems to be exported in the code.

[barmac]

It seems to work correctly when linked.

When linked to main on bpmn-js-properties-panel, the change does not break the editor (it's ignored and that's it).

[barmac]

✅ from me on this change. Looking forward to Nico's feedback.

[nikku]

Looks good to me.

#417 (comment) is what I'd consider to change.

[nikku]

@Buckwich this looks like it is good to be merged 🙂

[Buckwich]

I didn't want to interfere with the other fixes/issues in properties panel for the current release. I'll wait to merge until those are properly integrated