Better distinguish template tasks from plain service tasks

Is your feature request related to a problem? Please describe

In the properties panel template tasks are not really distinguishable from their standard BPMN counterparts:

What I need to do is look for the template section, and more specifically expand it to get hold on the template name.

Describe the solution you’d like

• The name of the template shall be more prominently displayed by the properties panel; in the screenshot above, it shall read SendGrid Email Template Task if the element template author chose that name:
• Going beyond that the properties panel shall display the element templates icon (cf. https://github.com/bpmn-io/internal-docs/issues/445, if specified).

Both help us to clearly distinguish templated tasks from the elements they are built upon:

Cf. design sketch:

Describe alternatives you’ve considered

Do nothing.

[nikku]

I’d go for option two: Understand that element templates is a thing and account for that. Consider however that elementTemplates may also not be used (i.e. handle it as an optional dependency).

Let us not make things super-dynamic at this stage.

[pinussilvestrus]

Edit: just saw the design sketch, which answers my question, sorry 🙂