Add FEEL Copilot link to popup editor

[philippfromme]

Proposed Changes

Adds a link to promote the new FEEL Copilot.

Checklist

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

• [x] Brief textual description of the changes present
• [x] 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}

[philippfromme]

cc @bastiankoerber

[nikku]

What about if we shorten this to "Learn FEEL", "Try co-pilot"?

Why the external launch link, when the thing clearly is a link?

[barmac]

If we merge this as is, this means that any @bpmn-io/properties-panel user is nudged to try out FEEL copilot, regardless if they use Camunda or not. While this may sound OK from the business perspective, this is still an MIT-licensed open source library. From that perspective, I'd rather expect the link to be plugged somehow in Camunda products instead of making it part of the upstream library. While we already have a link to the documentation in the source code, I think it's rather more stable than a link to an experimental project. TLDR: My suggestion is to make it pluggable, and implement the link downstream.

[barmac]

Also note that the link in its current form does not currently contain any UTM parameters, and with the current approach we cannot fix it easily as for each adjustment a change in this library needs to be integrated downstream.

[nikku]

Alternative: Move the popup editor out (make it a Camunda extension), and hence be free on how we integrate Camunda docs links there. Given past discussions on the editor, that could work, too.

[philippfromme]

I was expecting the pushback. I just wanted to avoid having to do a major refactoring for a single link. 🙈

[lmbateman]

What about if we shorten this to "Learn FEEL", "Try co-pilot"?

"Learn FEEL" works for me! For Copilot, I think there are a couple of things to to figure out.

1. Generally speaking, we'll have several Copilot LLMs, and we should think about whether, in the long run, it makes sense to refer to them all (individually and collectively) as "Copilot" in most cases, or whether we want to be more specific in most cases. My vision is that we would have a unified (but not exclusive) Copilot interface where the user can type any question/request, and an LLM sitting behind that interface can route the question to the correct LLM to take care of it (BPMN Copilot, FEEL Copilot, Camunda Docs AI, etc.). In that case, I think simply using "Copilot" would make more sense, since the user doesn't have to worry about whether the LLM they're interacting with can handle their prompt.
2. However, in this case, we're taking the user out of the Modeler to interact with a single LLM, so we may want to be specific ("FEEL Copilot") so they understand they can't ask it to generate BPMN. (Not that I expect anyone to try to use it to generate BPMN just yet, but it seems like the BPMN Copilot might make it into the product before the FEEL Copilot does.)

Why the external launch link, when the thing clearly is a link?

The design team decided to use the launch icon to indicate when a link takes you to an external site. (I personally tend to interpret it as "this link will open in a new tab", but I've just done some research and apparently not everyone shares that interpretation.)