Support read-only properties panel and entries

[philippfromme]

Is your feature request related to a problem? Please describe.

Due to the lack of support for read-only the Web Modeler has to roll their own solution for read-only https://github.com/camunda/web-modeler/issues/10705#issuecomment-2847242889. This is error prone and not the best solution.

Describe the solution you'd like

Add support for a read-only properties panel.

All entries read-only:

const modeler = new Modeler({
  additionalModules: [...],
  propertiesPanel: {
    parent: `#properties-panel`
    readOnly: true
  }
});

Specified entries read-only:

const modeler = new Modeler({
  additionalModules: [...],
  propertiesPanel: {
    parent: `#properties-panel`
    readOnly: {
      'fooEntry'
    }
  }
});

Describe alternatives you've considered

The alternative has already been implemented. 🤡

Additional context

Related to https://github.com/camunda/web-modeler/issues/10705

[philippfromme]

The properties panel already supports rendering entries as disabled. However, there are a couple of things missing to make this work:

1. properties-panel needs to support a disabled configuration similar to existing configurations (e.g. for errors)
2. bpmn-js-properties-panel and dmn-js-properties-panel need to support a configuration passed at instantiation time (e.g. descriptionConfig)
3. properties-panel needs to support setting a configuration at runtime similar to existing configurations (e.g. onSetErrors)
4. bpmn-js-properties-panel and dmn-js-properties-panel must account for the possibility of a read-only properties panel and not require any features that only exist in the modeler (e.g. modeling), so instead of const modeling = useService('modeling') it must be const modeling = useService('modeling', false)

[barmac]

Is it necessary that readonly mode can be activated dynamically? Perhaps we could implement a Viewer variant like in bpmn-js.

[philippfromme]

The events at runtime part and fine-grained control over what entries are read-only is optional. I like the idea of a viewer distribution. That would make configuration obsolete and would be consistent with bpmn-js and dmn-js. The downside of all of these is the none of them can be set to read-only at runtime without using hacks.

[wollefitz]

This is also related to https://github.com/camunda/web-modeler/issues/16245 where we need to make the properties panel read-only in Web Modeler if another user is editing the diagram currently.